Weave Code
Blaze Bundle Laravel Package
happyr/blaze-bundle
Symfony bundle for integrating the Blaze templating engine. It registers Blaze services, wires template configuration into Symfony, and lets you render lightweight templates from controllers and services with minimal setup.
Write down your routing mapping at one place
Frequently asked questions about Blaze Bundle
- Can I install happyr/blaze-bundle in a Laravel application?
- No. happyr/blaze-bundle is a Symfony bundle that depends on the Symfony Kernel, config/bundles.php registration, and the Symfony dependency injection container. Laravel has no bundle loader and uses service providers plus Illuminate\Container. You will also likely hit a hard Composer conflict because the bundle declares Symfony 5-era dependencies while Laravel pins symfony/* at ^6 or ^7.
- What does happyr/blaze-bundle actually do?
- It integrates the Blaze templating library with Symfony by registering Blaze services through the dependency injection container. It centralizes bundle configuration, wires template configuration into Symfony, and follows standard Symfony bundle conventions. It is not a Laravel package and provides no Laravel service provider or Blade integration.
- Is version 2.0.0 compatible with Laravel 10 or 11?
- No. Version 2.0.0 adds Symfony 5 and Twig 3 support only, which makes the package more Symfony-native rather than Laravel-compatible. It does not open a Symfony 6 or 7 path, and Laravel 10 and 11 rely on symfony/* ^6 or ^7. The release also implies PHP 8.0 or 8.1 support at best, with PHP 8.2 and 8.3 undocumented.
- What Symfony versions does happyr/blaze-bundle 2.0.0 support?
- The 2.0.0 release adds Symfony 5 and Twig 3 support. Symfony 5 is end-of-life, with 5.4 LTS security support ending in November 2025. There is no documented Symfony 6 or Symfony 7 path, so the package does not keep pace with modern Symfony or with Laravel's pinned symfony components.
- How do I configure Blaze services in Laravel?
- You cannot configure this bundle directly in Laravel because it relies on Symfony's DI extension, service definitions, tagged services, and compiler passes. A Laravel port would require reimplementing the bundle DI extension as a service provider, replacing Symfony service wiring with container bindings and Laravel tagging, and replacing Symfony Routing and HttpFoundation coupling with Laravel's router. That is a rewrite, not a configuration change.
- What Laravel features replace the Blaze bundle's entity-to-URL functionality?
- Laravel already covers roughly 90 percent of this domain with route model binding, the route helper, and URL signed routes. Route model binding resolves a parameter such as post to a Post model through getRouteKey, and route plus URL signedRoute handle URL generation. The residual is a thin convention layer, such as a HasCanonicalUrl-style interface and a small resolver service, which is cheaper to build natively.
- Does happyr/blaze-bundle work with Blade templates?
- No. The bundle's rendering path is exposed through Twig 3 extensions and templates, and Twig is a Symfony-specific integration surface. Laravel renders with Blade and has no Twig extension point to bind to. Porting the package means reimplementing its presentation layer in Blade as additional bespoke code.
- How do I test happyr/blaze-bundle in a Laravel project?
- You cannot meaningfully test this bundle inside a Laravel project because there is no Laravel integration to exercise. Any testing effort would target a fork, where you should cover service provider bindings, route resolution, and Blade rendering. Upstream also provides no documented failure modes, roughly zero dependents, and only about three stars, so there is little community test evidence to rely on.
- Is happyr/blaze-bundle maintained and safe for production?
- The maintenance signals are weak. Version 2.0.0 shipped with a single-line release note and no changelog, migration guide, or deprecation list. The project has roughly three stars, zero dependents, and no vendor backing. An unmaintained Symfony 5-era tree on a payment or PII path creates a code-ownership and audit obligation without creating a security response path.
- What are alternatives to happyr/blaze-bundle for Laravel?
- The practical alternative is to build the small convention layer natively in Laravel using route model binding, the route helper, and URL signed routes. A HasCanonicalUrl-style interface plus a resolver service covers the remaining behavior. Forking and porting this Symfony bundle is estimated at three to six engineer-days plus permanent fork ownership, compared with one to three days to build the equivalent natively.
Weaver
How can I help you explore Laravel packages today?