- What is tonysm/stimulus-laravel used for?
- It is a Laravel integration package for Stimulus.js that provides zero-config controller registration, Blade helpers, and Vite-friendly asset integration. It is intended for adding lightweight interactivity to server-rendered Blade views without adopting a full SPA framework. Teams using Hotwire-style progressive enhancement are the best fit.
- How do I install tonysm/stimulus-laravel?
- Install it with Composer using tonysm/stimulus-laravel, then configure your Laravel asset pipeline for Stimulus. The package is designed for zero-config controller registration and Vite-friendly workflows. Confirm your Stimulus bootstrap and asset entrypoints are configured once to avoid duplicate registration.
- Does stimulus-laravel support Laravel 13?
- The 1.5.0 release is noted as adding Laravel 13.x compatibility. That is a positive maintenance signal for teams planning a Laravel 13 upgrade. Before production adoption, confirm the exact Composer constraint and that the rest of your dependency graph is Laravel 13-ready.
- Is tonysm/stimulus-laravel compatible with Laravel 11 and 12?
- The evaluation does not confirm 11.x or 12.x support; it only highlights 1.5.0 as a Laravel 13.x compatibility release. Review the composer.json constraint and changelog before upgrading an older app. If the constraint drops older Laravel versions, treat it as a gated upgrade.
- How does zero-config controller registration work in Stimulus Laravel?
- The package auto-loads Stimulus controllers placed in a designated folder, so you avoid manually registering each controller. This is the zero-config controller registration described in the overview. Define folder and naming conventions early to prevent collisions as the number of controllers grows.
- Does Stimulus Laravel work with Vite?
- Yes, the package overview calls out seamless Vite integration for modern Laravel asset bundling. Validate Node and build tooling during staging, and confirm your Stimulus bootstrap runs only once. The evaluation flags duplicate Stimulus bootstrapping and asset pipeline misconfiguration as key operational risks.
- How do I test Stimulus controllers in a Laravel app?
- Run the package tests or a staging build, then pilot Stimulus in one low-risk Blade view or component. Browser smoke tests should confirm controller lifecycle behavior and compiled assets. Document controller registration and testing conventions early so coverage stays consistent.
- Is tonysm/stimulus-laravel safe for production?
- The evaluation rates technical risk as low-to-moderate because the package is a thin integration layer. The main production concerns are Laravel version coupling and asset-pipeline assumptions, not deep runtime behavior. Pin versions, confirm Laravel 13 readiness across your dependency graph, and have a fallback plan if maintenance stalls.
- What are alternatives to stimulus-laravel?
- Alternatives include a plain Stimulus setup without a Laravel wrapper, Hotwire/Turbo for broader progressive enhancement, or Inertia with React or Vue for a full SPA-style frontend. Stimulus Laravel is best when you want Blade-first interactivity with less controller registration boilerplate. Teams already standardized on a JavaScript framework may not need it.
- Is stimulus-laravel actively maintained?
- The 1.5.0 release suggests maintainers are tracking Laravel releases, which is a positive support signal. It remains a community-supported open-source package, so your team should own upgrade validation. Monitor upstream Laravel and Stimulus changes and keep a removal fallback if maintenance slows.