Weave Code
Livewire Twig Laravel Package
enflow/livewire-twig
Integrates Twig templating with Laravel Livewire, letting components render Twig views while retaining Livewire’s reactive behavior. Ideal for Laravel projects or teams already standardized on Twig-style templates.
Add Livewire components in your Twig templates
Frequently asked questions about Livewire Twig
- How do I install enflow/livewire-twig in a Laravel project?
- Install with composer require enflow/livewire-twig, publish the package configuration, and register the service provider. The install itself is trivial; the real work is confirming the supported Laravel, Livewire, and TwigBridge versions and proving that Livewire directives have faithful Twig equivalents. Plan a small spike before rolling it out.
- Does enflow/livewire-twig support Livewire 3 and Laravel 10, 11, or 12?
- The plausible target stack is Laravel 10/11/12 with Livewire 3.x and TwigBridge, but the exact supported triple must be confirmed from composer.json constraints and CI rather than assumed. The 4.6.0 release has no described changes, so verify whether the Livewire or TwigBridge floor or ceiling moved. There is no confirmed Livewire 4 compatibility plan in the provided context.
- Can I use Twig and Blade Livewire components in the same Laravel app?
- Yes, coexistence is the only defensible migration model: keep Blade as the default and fallback and allow Twig only for new components in a designated domain. Do not convert existing Blade components, because third-party Livewire packages ship Blade views and cannot be converted. A mixed-mode application is the most likely source of surprise, so audit dependencies first.
- How are Livewire directives like wire:model and @entangle written in Twig?
- The package must provide faithful Twig equivalents for Livewire's directive surface, including wire:* attributes, @entangle, and @livewire. That integration is plausible but cannot be verified from the 4.6.0 release because it has no changelog. Test each directive your components use in a timeboxed spike before relying on it.
- Is enflow/livewire-twig production ready?
- The assessment is conditional and baseline only, with no production commitment. Release 4.6.0 shipped with a bare compare link and no described changes, so it must be re-confirmed against the 4.5.0 to 4.6.0 diff before scheduling. Treat it as a spike candidate and pin the package, Livewire, and TwigBridge versions.
- How well is livewire-twig tested against real Livewire lifecycle behavior?
- The test suite needs to cover hydration, computed properties, file uploads, pagination, model binding, and events, not just happy-path rendering. The provided context does not confirm what the suite actually covers, so ask the maintainer and review CI yourself. Add your own integration tests for the directives and lifecycle paths your app uses.
- What changed in livewire-twig 4.6.0?
- Release 4.6.0 was published with a bare compare link and no described changes, so the exact changes are unknown from the release notes. Diff 4.5.0 to 4.6.0 commit by commit and check composer.json for constraint deltas, especially the Livewire and TwigBridge floors or ceilings. A semver-minor bump implies backwards-compatible additions, but an unpinned constraint shift can still break builds silently.
- Does livewire-twig work with third-party Livewire packages that use Blade views?
- Third-party Livewire packages ship Blade views and extend Livewire classes, so they will not respect Twig rendering and cannot be converted. Wrap or exclude them, and audit the Livewire dependency tree for packages that publish Blade views or extend the component base class. This is why a mixed-mode application needs explicit boundaries.
- How do I migrate an existing Laravel Blade app to Twig with Livewire?
- Do not convert existing Blade components. Use coexistence: Blade remains the default and fallback, while Twig is permitted only for new components inside a designated domain. Adoption is only justified where Twig is already a house standard, such as an inherited Symfony, Drupal, or Pattern Lab front end; in a standard Blade shop the second dialect adds cost with no payoff.
- What are the maintenance and version-coupling risks of using livewire-twig?
- The highest risk is version coupling, because the package reaches into Livewire's rendering internals and is structurally exposed to Livewire minor releases. Pin the package, Livewire, and TwigBridge, run that exact triple in CI, and confirm the integration uses public Livewire extension points rather than monkey-patching. Also check maintainer capacity, issue responsiveness, support window, and license or upgrade policy.
Weaver
How can I help you explore Laravel packages today?