Weave Code
Stimulus Bundle Laravel Package
symfony/stimulus-bundle
Symfony bundle that integrates Stimulus with Symfony and Symfony UX. Adds Twig stimulus_* helpers for controllers/actions/targets, supports AssetMapper, and provides a service to build Stimulus data attributes for use in templates and services.
Integration with your Symfony app & Stimulus!
Frequently asked questions about Stimulus Bundle
- Can I use Symfony’s StimulusBundle in a Laravel project?
- No, the bundle is designed exclusively for Symfony and relies on its Twig templating, AssetMapper, and Dependency Injection system. Laravel’s Blade, Mix/Vite, and Service Container make direct integration impossible without significant rewrites.
- What’s the best way to add Stimulus to Laravel without Symfony dependencies?
- Use NPM packages like `stimulus` or `stimulus-use` alongside Laravel Mix or Vite. These tools integrate natively with Laravel’s asset pipeline and Blade templates, avoiding Symfony’s architecture entirely.
- Will this bundle work with Laravel’s Blade templating?
- No, the bundle’s Twig helpers (`stimulus_*`) cannot be used in Blade. You’d need to manually write Stimulus data attributes or create custom Blade directives, which defeats the bundle’s purpose.
- Does StimulusBundle support Laravel’s asset pipeline (Mix/Vite)?
- No, it relies on Symfony’s AssetMapper, which is incompatible with Laravel Mix or Vite. You’d need to manually configure asset compilation or abandon the bundle’s asset features.
- What Laravel versions does this bundle support?
- None. The bundle is Symfony-focused and has no official Laravel support. Attempting to use it would require unsupported workarounds, risking instability and security issues.
- Can I use Symfony UX features from this bundle in Laravel?
- No, Symfony UX is tightly coupled with the bundle’s architecture. Laravel lacks equivalent frontend tooling, so you’d need to replicate features manually or use Laravel-specific alternatives like Vite plugins.
- Are there performance risks from adding Symfony dependencies?
- Yes, introducing Symfony components (e.g., `symfony/ux`, `symfony/asset-mapper`) would bloat your project, increase bundle size, and risk conflicts with Laravel’s autoloader and DI container.
- How would I migrate from this bundle to a Laravel-native solution?
- You wouldn’t. The bundle cannot be ported to Laravel—its core features (Twig, AssetMapper, Symfony UX) are fundamentally incompatible. Start fresh with NPM-based Stimulus integration instead.
- Does this bundle provide unique benefits over manual Stimulus setup?
- No, manual integration via NPM already offers the same functionality (controllers, actions, targets) without Symfony’s overhead. The bundle adds no value for Laravel developers.
- Who maintains this bundle for Laravel, and where can I get support?
- The bundle is maintained by Symfony’s team, not Laravel. Support is Symfony-focused, and issues specific to Laravel would require unsupported workarounds or community help—if available.
Weaver
How can I help you explore Laravel packages today?