- What is emaia/laravel-hotwire used for?
- It is a Laravel package for building Hotwire applications with Turbo Drive, Turbo Frames, Turbo Streams, Stimulus controllers, and Blade components. It is aimed at Blade-first Laravel monoliths that want reactive, server-rendered interfaces with minimal JavaScript. It also provides selective CSS preset bundles and Artisan diagnostics for asset and component checks.
- How do I install Laravel Hotwire in a Laravel app?
- Install it with Composer as emaia/laravel-hotwire, then follow the package setup for Blade components, Stimulus assets, and CSS presets in your Vite/Tailwind pipeline. The package uses Artisan commands such as hotwire:bundle-preset and hotwire:check --fix for bundle generation and diagnostics. Confirm the current Laravel/PHP constraints and configuration steps in the README before upgrading.
- Which Laravel and PHP versions does laravel-hotwire support?
- The exact Laravel and PHP support matrix is declared by the package in its composer.json and release notes, so check those before installing. The package is pre-1.0, so constraints and behavior can change between minor releases. Validate the chosen version against your Laravel, Vite, and Tailwind setup in a test branch.
- Do I need to write JavaScript to use Turbo Frames and Turbo Streams with this package?
- The package is designed for server-rendered HTML with Turbo Drive, Turbo Frames, and Turbo Streams, so most interactions are driven by Blade templates and Turbo responses rather than custom JavaScript. Stimulus controllers are included for behavior that needs client-side hooks. You should still review your Turbo Stream targets and frame navigation patterns for the intended UX.
- Are hw: Blade short tags safe to use inside PHP strings and component attributes?
- Blade short-tag compilation is described as safer in 0.81.0, but it can still alter edge-case output in PHP strings, heredocs, and attributes. After upgrading, inspect compiled or rendered output where hw: tags appear in those contexts. Regression-test the affected views rather than assuming identical output.
- How do selective CSS preset bundles work in laravel-hotwire?
- Selective bundles let you generate CSS presets based on recorded component selections instead of shipping the full preset set. In 0.81.0, selective bundle plans move to component-only v2, so existing plans may need regeneration. Use hotwire:bundle-preset with the documented --from option and keep generated plans version-controlled.
- What changed in laravel-hotwire 0.81.0 that I need to review before upgrading?
- 0.81.0 changes direct video URL ownership to the package's no-JS video embed and shifts selective bundle plans to component-only v2. It also improves asset governance with replayable selective preset regeneration and safer Blade short-tag compilation. Review the upgrade guide, regenerate affected bundle plans, and test video embeds before rollout.
- How does the no-JS video embed handle YouTube and Vimeo URLs?
- The video embed renders server-side for direct YouTube and Vimeo URLs, reducing custom oEmbed JavaScript and working in no-JS environments. Unsupported providers fall back to a link instead of an embed. Configure responsive sizing, loading behavior, accessible titles, and YouTube privacy mode, and check CSP rules for third-party iframes.
- What does hotwire:check --fix do and can I run it in CI?
- It runs Artisan diagnostics and can regenerate untouched package drift with --fix, but it is not a substitute for reviewing application edits. The package must preserve your edits and validate invalid plans or removed presets, so run --fix only after inspecting diffs. In CI, use diagnostics as a check and keep automatic fixes in a controlled job or isolated branch.
- Is emaia/laravel-hotwire production-ready and how is it maintained?
- It is a pre-1.0 package, so minor releases can include behavior changes and you should track release notes actively. The package provides diagnostics and recovery paths, but it appears community-supported, so plan for internal ownership and documentation. Validate bundle regeneration, video embed fallbacks, and Sidebar interaction regressions in staging before production.