Laravel Hotwire Laravel Package

The complete Hotwire stack for Laravel — Turbo Drive, Turbo Streams, Stimulus controllers and Blade components.

Stimulus JS framework -- client-side behavior via HTML data attributes, zero server round-trips. Use when creating controllers for DOM manipulation, handling click/input/submit events, managing targets and values, wiring outlets between controllers, wrapping third-party JS libraries, or building toggles, dropdowns, modals, tabs, clipboard interactions. Code triggers [data-controller, data-action, data-target, data-*-value, data-*-class, data-*-outlet, connect(), disconnect(), static targets, static values]. Also trigger when the user asks "how do I add a click handler", "how to toggle a class", "how to build a dropdown/modal/tabs", "how to wrap a JS library", "add keyboard shortcuts", "lazy-load a controller", "listen to global events", "communicate between controllers". Do NOT trigger for partial page updates without JS (use turbo), or reusable blade components.

Hotwire Turbo => SPA-like speed with zero JavaScript. Covers Drive (full-page navigation), Frames (partial page sections), and Streams (multi-target updates). Use when building ajax navigation, lazy-loaded page sections, inline editing, pagination without reload, modals loaded from the server, flash messages via streams, real-time updates, or multi-section page updates. Code triggers => turbo-frame, turbo-stream, data-turbo-frame, data-turbo, data-turbo-action, turbo_stream(), TurboResponse, wantsTurboStream(), wasFromTurboFrame(), dom_id(), dom_class(), x-turbo::stream, x-turbo::frame. Also trigger when the user asks "how to update part of the page without reload", "how to make navigation feel like SPA", "how to lazy-load a section", "how to do inline editing", "how to push real-time updates from server". Do NOT trigger for client-side JS behavior (use stimulus) or reusable static UI.