- How do I install imliam/laravel-blade-helper?
- Install it with Composer using composer require imliam/laravel-blade-helper. The package registers its service provider through Laravel package auto-discovery, so no manual provider registration is normally required. There is no npm build step or infrastructure change involved, making it a Composer-only addition to your application.
- What does laravel-blade-helper actually do for custom Blade directives?
- It is developer tooling layered on top of Blade that makes authoring and registering custom Blade directives and helpers easier. Rather than changing how Blade renders views at runtime, it reduces the boilerplate you write when defining your own directives. The result is cleaner, more readable templates with less repeated markup.
- Which Laravel versions does imliam/laravel-blade-helper support?
- Version 1.7.0 added support for Laravel 13, and the package is already in use on Laravel 11 and 12 applications. Because that support arrived in a minor release, confirm whether the constraint targets a stable ^13.0 or requires a dev or beta stability flag before adopting it on a pre-GA framework. If your application is staying on Laravel 11 or 12, the release is purely additive and you can fold it into a routine dependency sweep.
- Is v1.7.0 a breaking change and do I need to update my code?
- No. The v1.7.0 changelog contains only an addition (Laravel 13 constraint support) plus internal test-suite modernisation such as the move to PHPUnit 12 and #[Test] attributes, with nothing removed or renamed. Consumer-facing work is effectively composer update plus a test run. The PHPUnit changes are confined to the package's own require-dev graph and are not installed transitively into your application.
- Should I put laravel-blade-helper in require or require-dev?
- Because the package is authoring-time tooling, it can often sit in require-dev, but only if nothing in production references artifacts it generates or registers. If your custom directives are registered by the package's service provider during view rendering, it needs to stay in require. Verify which mode you rely on before moving it, since this is the highest-leverage decision available.
- Do I need to register the service provider manually or publish config files?
- The service provider is registered via Laravel package auto-discovery, so manual registration in config/app.php is typically unnecessary. The changelog for v1.7.0 does not list any changes to artisan command names or generated file locations. If the package publishes config, assets, or generated IDE-helper files in your setup, re-publish or regenerate them after upgrading to be safe.
- Will this package affect production performance or view rendering?
- No meaningful impact. The package does not own persistence, routing, queues, or the request path; its work happens at authoring and build time, and Blade compiles directives into plain PHP that is then cached. The realistic blast radius of a bad version is limited to view compilation and developer workflow rather than runtime data or request handling.
- Can I use laravel-blade-helper alongside the native Blade::directive() API?
- Yes. The package augments how custom Blade directives and helpers are authored and registered rather than replacing Blade itself, so Laravel's built-in Blade::directive() and Blade::if() approaches continue to work. That makes it easy to adopt incrementally, converting only the directives where the boilerplate savings matter. You can also skip it entirely if the native API already covers your use case.
- How do I test custom Blade directives built with this package?
- Test them like any other Blade directive: render a view in a feature or unit test and assert on the resulting output or compiled string. The package's own PHPUnit 12 and #[Test] attribute migration is internal to its require-dev dependencies and does not change your test stack. Running your existing suite after composer update is a sufficient sanity check for a minor release like 1.7.0.
- Is laravel-blade-helper actively maintained, and what are the alternatives?
- Yes, it is framework-tracking: v1.7.0 added Laravel 13 support and modernised its test suite to the current PHPUnit schema, which are positive maintenance signals. The main caveat is that it is a single-maintainer project, so consider bus factor and pin sensibly. Alternatives are Laravel's native Blade::directive() and Blade::if() helpers, which cover many cases without any additional dependency.