emaia/laravel-hotwire
Laravel Hotwire brings Turbo and Stimulus to your Laravel app, trimming JavaScript while keeping pages fast and reactive. Integrates seamlessly with Blade, delivering SPA-like navigation with minimal setup.
hw: components, selective CSS preset bundles, Artisan diagnostics, and now a stronger overlay-host model for Modal, Sheet, and Drawer workflows. 0.83.0 adds reusable overlay hosts with multiple independent/nested openings, per-opening presentation, server-driven open/returnFromOverlay/closeOverlay responses, contextual returns via <hw:overlay-return>, instance-scoped closing, and optional error-focus on <hw:form>. Fits Laravel monoliths and Blade-heavy Hotwire apps with complex form/dialog flows; less relevant for API-only or non-Hotwire frontends.$request->overlayOrigin() for frame-backed openings, explicit origin:/source: context for stream openings, and replacement of removed modal-auto-close patterns with closeOverlay(). Published controller copies must be removed and assets rebuilt.modal-auto-close, changes frame-backed overlay instance IDs, requires origin: for child stream openings and source: when a fragment contains a form, and drops support for host:, result:, and package-managed return renderers. Existing overlays, custom published controllers, and auto-close marker appends are the primary breakage surface. Focus and autofocus changes need regression coverage. The Tiptap dependency group moves to 3.32.0, adding a frontend dependency validation point.modal-auto-close removal? How are existing host:/result: overlay returns detected and migrated? Are published controller copies detected by diagnostics? How should teams guard overlayOrigin() returning null for actions that also serve page requests? Do nested overlays and browser back/forward behave predictably? What accessibility guarantees exist for focus return, error-focus, and delayed Rich Text initialization? Can asset rebuilds and overlay migrations run safely in CI? Does Tiptap 3.32.0 introduce editor regressions?modal-auto-close markers, published controller copies, and custom return renderers. Replace auto-close marker appends with closeOverlay(), remove published controller copies, rebuild assets, migrate stream openings to explicit origin:/source:, and use $request->overlayOrigin() with null guards. Replace host:/result:/package-managed returns with returnFromOverlay($origin, $content) or native Turbo Frames. Run hotwire:check --fix where applicable, inspect diffs, and validate Blade hw: tags in PHP strings, heredocs, and attributes.error-focus, and autofocus fallback to Dropdown/Popover triggers. Check CSP rules for video iframes and any overlay/Turbo stream behavior. Regression-test the Sidebar click fix and existing bundle presets.modal-auto-close and removed return-renderer patterns; 4) update stream openings and overlayOrigin() usage; 5) rebuild assets and remove published controller copies; 6) validate focus, validation, nested overlays, and Turbo refresh behavior in staging; 7) production rollout with rollback plan.error-focus and improved focus return reduce accessibility/support burden. However, package appears community-supported; plan for internal ownership. Maintain migration notes for modal-auto-close, overlayOrigin(), and contextual returns.modal-auto-close migration causes overlays not to close as expected. Stale published controllers or un rebuilt assets can preserve old behavior. Stream openings without origin:/source: fail. overlayOrigin() may be null for page requests. Replaced return destinations fail safely but may leave missing content. Focus edge cases remain possible with delayed Rich Text initialization. Tiptap 3.32.0 may introduce editor regressions. Unsupported video providers still fall back to a link.How can I help you explore Laravel packages today?