Weave Code
Stimulus Laravel Laravel Package
hotwired-laravel/stimulus-laravel
Stimulus-Laravel integrates Hotwired Stimulus with Laravel, helping you register and load Stimulus controllers and attach them in Blade via data-controller attributes, adding lightweight interactive UI without a full SPA or heavy JavaScript framework.
Use Stimulus in your Laravel app
Frequently asked questions about Stimulus Laravel
- How do I install hotwired-laravel/stimulus-laravel in a Laravel application?
- Install it with Composer using composer require hotwired-laravel/stimulus-laravel, then publish the package config and assets with the provided artisan vendor:publish command. Because it is a thin convention layer rather than a runtime service, there is no database, queue, or auth setup to configure. After publishing, wire the Stimulus entrypoint into your JavaScript build so the controllers are actually compiled and loaded in the browser.
- Which Laravel versions does stimulus-laravel support?
- Release 1.5.0 was shipped specifically as a Laravel 13.x compatibility release, so that is the headline version to target. The 1.5.0 changelog contains only that compatibility change, so you should read the exact illuminate/* constraint in its composer.json to confirm whether Laravel 11 and 12 are still allowed or were dropped. Always cross-check the PHP version floor implied by your Laravel major, since that will gate you before the package does.
- Do I need Vite to use stimulus-laravel?
- Yes, in practice you need a JavaScript bundler, and Vite is what current Laravel skeletons ship with. The package handles the PHP-side registration and Blade helpers; the actual Stimulus controllers must still be compiled through your front-end pipeline. The main friction point in adoption is coordinating the PHP-side registration with the vite.config.js entrypoint, not anything architectural.
- How do I attach a Stimulus controller to a Blade view with this package?
- You attach controllers the standard Stimulus way by adding data-controller attributes to your Blade markup, for example data-controller="hello" on any element. The package's job is making sure the corresponding controller is registered and loaded so that attribute resolves at runtime. This means you can add interactivity view by view without restructuring your templates.
- Does stimulus-laravel work with Livewire or Inertia?
- It technically installs alongside them, but it is largely unnecessary for apps built on Livewire, Inertia, or a full SPA front end. The package exists to support the Hotwire approach, where Stimulus provides modest progressive enhancement to server-rendered Blade markup. If your team has standardized on a component framework, this package is dead weight and should be declined.
- Do I need turbo-laravel to use stimulus-laravel?
- Stimulus can be used on its own for lightweight interactive UI, but the package is designed as the modest-JS companion to Turbo and fits best in apps already using or planning to use turbo-laravel. If you are moving to Hotwire, plan to adopt both packages and treat their version upgrades as related work. Check whether a matching turbo-laravel release is required when you upgrade Laravel, since the two tend to move together in practice.
- Where do my Stimulus controllers live and how are they registered?
- Controllers are plain JavaScript files loaded through your bundler's Stimulus entrypoint, typically using the standard Stimulus application register call. The package wires controller registration and asset publishing into Laravel's service container and Blade layer so you get a convention rather than a heavy runtime. Keep the PHP-side configuration and the JavaScript entrypoint in sync whenever you add a new controller.
- Is stimulus-laravel a good alternative to Livewire or Alpine.js?
- It solves a different problem: Stimulus gives you small, reusable controllers that attach behavior to existing server-rendered markup, rather than managing component state like Livewire does. Alpine is closer in spirit, but Stimulus favors explicit controller classes in separate files over inline attributes. Choose it when you want progressive enhancement on Blade views without adopting a full component framework or SPA.
- Is stimulus-laravel safe to use in production and how actively is it maintained?
- The technical risk is low to moderate and mostly version-shaped rather than logic-shaped: compatibility patches do land, but they land reactively after a Laravel major release, and the project is small and volunteer-led. Release 1.5.0 contains a single Laravel 13 compatibility change, meaning the feature surface and any known issues are inherited unchanged from 1.4.0. Plan for some lag on framework upgrades and gate your Laravel upgrade on this package's release.
- Should I upgrade from 1.4.0 to 1.5.0 and how do I test it?
- If you are moving to Laravel 13, upgrade Laravel first, then this package, then turbo-laravel, validating the JavaScript build between each step. If you are staying pinned to an older Laravel, 1.5.0 delivers no functional value, so stay on 1.4.0 and take the bump with your next routine dependency sweep. Test by exercising the Blade views that use data-controller attributes in a browser or a feature test that asserts the markup, and confirm the compiled assets still load after the bump.
Weaver
How can I help you explore Laravel packages today?