Register blade directive after resolving service
Register blade directive after resolving service

More efficient way (IMHO) to register the blade directive, to make sure it's only registered when `blade.compiler` service is resolved (we're browsing from web and we're rendering blade views already), otherwise we neither need to attach the directive nor resolve the `blade.compiler` at this stage. Using the `Blade::directive` facade will auto resolve the `blade.compiler` service even if we're interacting with the application from CLI through artisan, which in some project setups it may cause some `InvalidArgumentException` exceptions (Route [name] not defined.)
tightenco/ziggy,tightenco/ziggy