Extend the "compile" function on BladeCompiler.php

One option:

You can define your own ViewServiceProvider which extends the Laravel one. You would then need to override the registerBladeEngine method - this is where the Blade Compiler is bound into the container:

public function registerBladeEngine($resolver)
{
    $this->app->singleton('blade.compiler', function () {
        return new MyBladeCompiler(
            $this->app['files'], $this->app['config']['view.compiled']
        );
    });

    $resolver->register('blade', function () {
        return new CompilerEngine($this->app['blade.compiler']);
    });
    }

MyBladeCompiler extends the Laravel BladeCompiler and overrides the compile method with your implementation.

Finally, swap the Illuminate\View\ViewServiceProvider::class out of the config/app.php providers array, and replace it with your own ViewServiceProvider.

@tykus Thank you very much!! Your insight led me to the solution of my problem.

I did the following:

1. Created a new service provider with php artisan make:provider ViewServiceProvider and filled the provider with the register data. (I had to copy ALL the contents of the Illuminate\View\ViewServiceProvider class, @tykus if you know how can I avoid that, would be great)

2. Created a class called customBladeCompiler, extending the original BladeCompiler.php and overrided the compile method like this:

class customBladeCompiler extends BladeCompiler {
    /**
     * Compile the view at the given path.
     *
     * @param  string $path
     * @return void
     */
    public function compile($path = null) {
        if ($path) {
            $this->setPath($path);
        }

        if (!is_null($this->cachePath)) {
            if (function_exists('ioncube_read_file')) {
                $contents = $this->compileString(ioncube_read_file($this->getPath()));
            } else {
                $contents = $this->compileString($this->files->get($this->getPath()));
            }

            $this->files->put($this->getCompiledPath($this->getPath()), $contents);
        }
    }
}

1. Swaped the Illuminate\View\ViewServiceProvider::class out of the config/app.php providers array, and replaced it with my own ViewServiceProvider:

        //Illuminate\View\ViewServiceProvider::class,

        /*
         * Custom View Service Provider
         */

        App\Providers\ViewServiceProvider::class,

@Lvkz you can extend the Laravel ViewServiceProvider as I mentioned in the original reply, then you only need to implement/override your custom method(s). This is exactly what you have also done with the BladeCompiler.

This should be the entire contents of your ViewServiceProvider

namespace App\Providers;

use Path/To/MyBladeCompiler;

class ViewServiceProvider extends \Illuminate\View\ViewServiceProvider
{
    public function registerBladeEngine($resolver)
    {
        $this->app->singleton('blade.compiler', function () {
            return new MyBladeCompiler(
                $this->app['files'], $this->app['config']['view.compiled']
            );
    });

    $resolver->register('blade', function () {
        return new CompilerEngine($this->app['blade.compiler']);
    });
    }
}

@tykus Oh, that was dumb of me... Heheheh... Thank you very much!!! It worked like a charm!!!