- What is tonysm/turbo-laravel and what does it do?
- Turbo Laravel is a Composer package that adds Hotwire Turbo conventions to Laravel applications. It wires Turbo Drive, Turbo Frames, and Turbo Streams into Laravel's response handling and Blade views, so you get SPA-like navigation and partial page updates while still rendering HTML on the server. The goal is reactive pages with minimal custom JavaScript rather than a full frontend framework.
- How do I install turbo-laravel in a Laravel application?
- Install it with Composer using composer require tonysm/turbo-laravel, then run the package's install command to publish its configuration and any frontend assets you need. Add Turbo to your JavaScript bundle and include it on the pages where you want Turbo enabled. Adoption can be incremental, so you can start with a single section of the app before rolling Turbo out everywhere.
- Which Laravel and PHP versions does turbo-laravel 2.6.0 support?
- Version 2.6.0 is a minor release whose main change is adding Laravel 13.x compatibility, and it declares no breaking changes. The exact PHP and Laravel constraint ranges live in the package's composer.json, so check those before upgrading. If your application is not yet on a supported Laravel version, stay on the latest 2.x release that matches your platform until the framework upgrade is done.
- Do I need to change any code when upgrading from 2.5.1 to 2.6.0?
- The 2.6.0 release is described as a single compatibility change with no declared breaking changes, so it should be a low-effort minor upgrade under semver. Update the constraint to ^2.6.0, resolve dependencies with Composer, and run your test suite. Then smoke-test Turbo Drive navigation, Frames, Streams, form submissions, redirects, and error responses, and diff any published config or asset files.
- Do I need Node.js or a JavaScript build step to use Turbo Laravel?
- You still need to get the Turbo JavaScript library into your frontend, which normally means a build step such as Vite. The package itself handles the Laravel side: response conventions, Blade helpers, and Stream rendering. If your app already compiles assets, adding Turbo is a small addition to that existing pipeline.
- Can Turbo Laravel be used together with Livewire or Inertia?
- It is technically possible, but the fit is best for Blade-centric applications that render HTML on the server. Inertia, React, and Vue already own navigation and page transitions, so Turbo Drive can overlap with them and you should define clear boundaries first. Livewire-heavy apps should likewise be validated screen by screen, because both tools want to control partial updates.
- How do Turbo Frames and Turbo Streams work with Laravel Blade?
- Turbo Frames let a page request and swap just one section of HTML, which maps naturally to Blade partials and dedicated controller actions. Turbo Streams let a single response update multiple parts of the page, which suits create, update, and delete flows where several fragments change at once. The package provides helpers and conventions so those responses are built consistently from your Laravel controllers and views.
- How do I test Turbo Drive and Turbo Stream responses in Laravel?
- Treat Turbo endpoints like any other Laravel route: write HTTP tests that assert status codes, redirects, and the rendered HTML fragments. The package ships testing helpers for asserting Turbo Stream responses, so you can verify the stream targets and actions your controllers emit. Also add a few browser-level smoke tests for navigation and frame updates, since those behaviours depend on Turbo running in the page.
- What are the common production pitfalls with Turbo Laravel?
- Most issues come from responses that Turbo does not expect, such as redirects or error pages that fall outside your conventions, plus stale frames after caching. Watch navigation errors, stale frame content, and failed stream updates after deploying. Because 2.6.0 is compatibility-focused, functional risk to existing Turbo behaviour is limited, but a canary or staging deploy with monitoring is still worth doing.
- Is turbo-laravel actively maintained, and what are the alternatives?
- It is a community-maintained package, so treat it as a dependency with an internal owner, pin it to a minor range, and review releases alongside your Laravel upgrades. Alternatives include htmx-based packages, Livewire, and Inertia, depending on whether you want server-rendered fragments or a more JavaScript-driven frontend. For Blade apps that want minimal JavaScript, Turbo Laravel is one of the most direct options.