Download the PHP package emaia/laravel-hotwire without Composer

Laravel Hotwire

Laravel Hotwire is a server-driven UI toolkit for Laravel applications. It combines Turbo Drive, Turbo Frames, Turbo Streams, Stimulus controllers and Blade components so you can build fast, reactive interfaces with server-rendered HTML and focused client-side behavior.

Requirements

Laravel Hotwire requires PHP 8.3+, Laravel 12+, Vite, Tailwind CSS v4 and the DOM, libxml and mbstring PHP extensions.

Installation

Install the package with Composer:

Then scaffold the JavaScript, CSS and package dependencies:

The installer adds Stimulus, Turbo, @emaia/stimulus-lazy-loader, controller-specific npm dependencies, the @hotwire Vite alias, the controller loader, CSS preset imports and Laravel Idea metadata. Components work immediately after installation. You only publish controllers when you want to customize their source.

Publish configuration only when you need to change the component prefix or controller loading policy:

For lean installs, CI flags and loader details, see Advanced installation.

Documentation

Browse the same catalog from the terminal:

Components

Laravel Hotwire ships composable Blade components for common server-rendered UI patterns:

List everything available in your installed version:

Controllers

Package controllers auto-load from the vendor directory after hotwire:install. Use them directly with data-controller, or through the Blade components that mount them for you.

Standalone controllers include:

Publish a package controller only when you want to customize its source:

Styling

hotwire:install configures Tailwind with Nova by default and lists the other official presets as commented imports in resources/css/app.css. Uncomment Bloom and comment Nova, or select it while installing, for a chromatic, spacious and elevated visual language with restrained surface radii over the same components and controllers:

Override semantic hooks after the preset:

Or generate an application-owned preset:

For a layout with an explicit component set, generate a smaller visual bundle while retaining the shared structural foundation:

See Theming.

Check Your Setup

Check the controller loader, npm dependencies, published customizations and CSS contracts:

Imported application presets are validated automatically; --preset accepts a preset name or a path under resources/css for explicit CI checks. Run the application's production asset build separately to verify Tailwind utilities and imports. hotwire:check --fix regenerates the controller loader, untouched v2 selective CSS bundles and adds missing npm dependencies. Edited bundles and legacy plans remain manual. By default it also runs the detected package manager install command; use --skip-install when CI handles that separately.

Development

bun run build:css compiles every public preset plus a generated hotwire:bundle-preset bundle and application-owned clone for each one, then reports raw/gzip sizes. After an intentional output change, refresh the committed size baseline with bun run test:css:update.

The registry in src/Registry/catalog.php is the source of truth for package components, controllers, npm dependencies, docs paths and styling hooks. Update it whenever you add or rename a package component or controller.

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Contributions are welcome via pull requests.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

• Ednilson Maia
• All Contributors

License

The MIT License (MIT). Please see License File for more information.