Weave Code
Inertia Laravel Laravel Package
inertiajs/inertia-laravel
Laravel adapter for Inertia.js: build single-page apps using classic server-side routing and controllers. Provides middleware, helpers, and response macros to render Inertia pages, share props, handle versioning, and integrate seamlessly with Laravel.
The Laravel adapter for Inertia.js.
Frequently asked questions about Inertia Laravel
- How do I migrate an existing Laravel Blade app to Inertia.js without breaking existing routes?
- Replace `return view('page')` with `return Inertia::render('Page')` in your controllers. Use Blade components as Inertia page templates by wrapping them in `@inertia` directives. Start with non-critical routes and use feature flags to toggle Inertia routes incrementally. The Laravel adapter preserves middleware, validation, and auth logic, so most backend logic remains unchanged.
- Does Inertia.js Laravel support Server-Side Rendering (SSR) for better SEO?
- Yes, the package fully supports SSR via Laravel’s Blade + Inertia.js. Configure SSR by setting up the Laravel Vite plugin and ensuring your frontend assets are built for SSR. SSR improves SEO and initial load times, but requires Node.js/Vite setup. Test SSR in staging to avoid hydration mismatches or broken builds.
- Can I use Inertia.js with Laravel’s API routes (e.g., `Route::apiResource`)?
- Absolutely. Inertia.js works alongside Laravel’s API routes seamlessly. Use `Inertia::render()` for SPA-like responses or return traditional JSON responses for non-SPA endpoints. This hybrid approach lets you adopt Inertia incrementally while keeping existing API logic intact. Example: `Route::get('/dashboard', [DashboardController::class, 'index'])->name('dashboard');` with `return Inertia::render('Dashboard');` in the controller.
- What Laravel versions does `inertiajs/inertia-laravel` support?
- The package supports Laravel 9.x and 10.x (check the [GitHub releases](https://github.com/inertiajs/inertia-laravel/releases) for exact versions). For Laravel 8.x, use v0.3.x. Always pin the package version in `composer.json` to avoid breaking changes. The adapter aligns with Laravel’s release cycle, so updates typically include compatibility fixes.
- How do I handle form validation and redirects with Inertia.js in Laravel?
- Use Laravel’s built-in validation (e.g., Form Requests) and redirect with `Inertia::location()` or `Inertia::render()`. Flash data (e.g., errors) works automatically via Laravel’s `ShareErrorsFromSession` middleware. For client-side validation, use frontend frameworks (Vue/React) with Inertia’s `once` or `reload` props to sync state. Example: `return Inertia::render('Profile/Edit', ['errors' => $validator->errors()]);`
- What’s the best way to test Inertia.js pages in Laravel with Pest?
- Use Pest’s `assertInertia` and `assertInertiaFlash` helpers to test page renders, props, and flash messages. Example: `assertInertia(fn() => get('/dashboard'))->component('Dashboard')->location('/dashboard');`. Mock Inertia responses in unit tests with `Inertia::fake()`. For end-to-end testing, combine with Laravel’s HTTP tests or browser automation tools like Playwright.
- How do I optimize performance for Inertia.js pages with large payloads?
- Use `Inertia::share()` to cache global data (e.g., user auth) across requests. For dynamic data, leverage `once` or `reload` props to defer loading. Avoid over-fetching by structuring props carefully. Monitor payload sizes with Laravel Debugbar or Blackfire, and consider edge caching (e.g., Varnish) for SSR pages. Example: `Inertia::share(['auth' => fn() => Auth::user()]);`
- Can I use Inertia.js with multiple frontend frameworks (Vue, React, Svelte) in the same Laravel app?
- Yes, the Laravel adapter is framework-agnostic. Choose your frontend framework per route by configuring the `inertia` middleware or using `Inertia::setRootView()` for custom layouts. Example: `Inertia::setRootView('resources/js/app.vue')` for Vue or `resources/js/app.jsx` for React. Document the framework per route in your team’s architecture guide to avoid confusion.
- What are the alternatives to Inertia.js for Laravel SPAs, and when should I choose them?
- Alternatives include Laravel Livewire (for simpler SPAs with Blade), Next.js (for full-stack React apps), or traditional SPAs with Laravel as a backend API. Choose Inertia.js if you want to leverage Laravel’s routing, middleware, and validation while using Vue/React/Svelte. Livewire is better for Blade-heavy apps, while Next.js offers more frontend flexibility but requires a separate Node.js setup.
- How do I handle middleware conflicts between Inertia.js and Laravel’s default middleware stack?
- Place Inertia’s `HandleInertiaRequests` middleware **before** Laravel’s `ShareErrorsFromSession` to prevent flash data loss. Use `Inertia::disableSsr()` for non-SSR routes if conflicts arise. Document middleware order in your team’s Laravel setup guide. Example: In `app/Http/Kernel.php`, ensure `HandleInertiaRequests` appears before `ShareErrorsFromSession` in the `$middlewareGroups['web']` array.
Weaver
How can I help you explore Laravel packages today?