Weave Code
Turbo Laravel Laravel Package
hotwired-laravel/turbo-laravel
Turbo Laravel brings Hotwire Turbo to Laravel, delivering SPA-like speed with server-rendered HTML. It integrates Turbo Drive, Frames, and Streams with Blade helpers and page morphing, so you can build fast, reactive interfaces without writing custom JavaScript.
This package gives you a set of conventions to make the most out of Hotwire in Laravel.
Frequently asked questions about Turbo Laravel
- What is hotwired-laravel/turbo-laravel used for?
- It is a Laravel package that provides conventions and Blade helpers for using Hotwire Turbo in a server-rendered Laravel application. It integrates Turbo Drive, Turbo Frames, and Turbo Streams so you can get SPA-like navigation and partial page updates while still rendering HTML on the server. The goal is fast, reactive interfaces without building a separate JavaScript frontend.
- How do I install turbo-laravel in a Laravel app?
- Install it with Composer using the package name hotwired-laravel/turbo-laravel, then follow the package setup steps to publish configuration and add the Turbo JavaScript assets to your frontend build. You will typically register the Turbo assets in your layout and start using the provided Blade helpers and response conventions. Check the package requirements against your Laravel and PHP versions before installing.
- Does turbo-laravel support Laravel 13?
- Yes, release 2.6.0 adds Laravel 13.x compatibility, making the package viable for greenfield Laravel 13 projects and planned upgrades. You should still verify your PHP version, Composer constraints, and frontend build tooling against the package requirements. Review the changelog and CI test matrix if Laravel 13 support is critical to your rollout.
- What is the difference between Turbo Drive, Frames, and Streams in Laravel?
- Turbo Drive intercepts link clicks and form submissions to swap the page body without a full reload, giving faster navigation. Turbo Frames let you scope updates to a specific part of the page by wrapping it in a frame element and returning partial HTML. Turbo Streams return targeted HTML fragments and actions that update or replace specific elements after a form submission or other mutation.
- Do I need to write JavaScript to use Turbo Laravel?
- In most cases no, because the package is designed around server-rendered Blade templates and HTML responses. You add the Turbo JavaScript library to your asset pipeline, but day-to-day work happens in routes, controllers, Blade views, and Turbo Frame or Stream responses. Custom JavaScript is only needed for behavior Turbo does not cover, such as third-party scripts that must be reinitialized after navigation.
- How does turbo-laravel handle redirects, CSRF, and flash messages?
- Turbo Laravel follows Turbo conventions so redirects from controllers are followed by Turbo Drive and form submissions include CSRF tokens through standard Laravel mechanisms. Flash messages and validation errors are rendered in the returned HTML, but you need to place them where Turbo will actually update them, often inside a frame or stream target. Teams should deliberately test redirect behavior, authorization failures, and error rendering under Turbo navigation.
- Can I use turbo-laravel with Livewire or Inertia?
- It is technically possible to install the package alongside other frontend stacks, but Turbo overlaps with Inertia's client-side routing and with Livewire's component update model. The package is best suited to Blade monoliths pursuing progressive enhancement rather than apps already committed to Inertia or Livewire-heavy interaction patterns. If you use them together, scope Turbo to isolated pages and confirm that navigation and DOM updates do not conflict.
- How do I migrate an existing Laravel app to Turbo Laravel incrementally?
- Start with a bounded pilot area such as a dashboard, index page, or simple form workflow, and introduce Turbo Drive first for navigation. Then add one Turbo Frame for an isolated partial update and one Turbo Stream form flow for a targeted mutation. Establish regression tests for redirects, CSRF, validation errors, flash messages, and authorization failures before expanding to more complex screens.
- What are the production risks of using Turbo Laravel?
- The main risks are Turbo JavaScript version alignment, behavior differences in navigation and frame rendering, and hidden coupling in existing Blade and JavaScript patterns. Third-party scripts and event handlers that assume full page loads may need adjustment, and you should document a fallback to full-page requests if regressions appear. Since 2.6.0 is a minor compatibility release, breaking-change risk is likely low but should be confirmed against the changelog and your dependency matrix.
- Is turbo-laravel actively maintained and what are the alternatives?
- Release 2.6.0 signals active maintenance and Laravel 13 readiness, and the project is a community-maintained Hotwire integration for Laravel. Maintenance work mainly involves tracking Laravel major releases, Turbo JS updates, and frontend asset pipeline changes. Alternatives include Inertia with Vue or React, Livewire for component-driven interactivity, or hand-rolled Turbo integration, depending on how much client-side JavaScript your team wants to own.
Weaver
How can I help you explore Laravel packages today?