Weave Code
Inertiajs Laravel Package
laravel-frontend-presets/inertiajs
A Laravel frontend preset that scaffolds Inertia.js in a fresh app, wiring up authentication, layouts, and example pages so you can skip manual setup and start building single-page apps with Laravel as the backend and Vue or React on the frontend.
A Laravel frontend preset to get you up and running with Inertia.js
Frequently asked questions about Inertiajs
- How do I install laravel-frontend-presets/inertiajs?
- You add it as a dev dependency with Composer and then run the preset command, which copies its stubs, controllers, layouts, and asset pipeline config into a fresh Laravel app. This only works on the legacy Laravel versions the package targets, because the artisan preset command it depends on no longer exists in modern Laravel. There is no supported installation path for a current Laravel 10, 11, or 12 application.
- Which Laravel versions does this Inertia preset support?
- Release 0.4.0 widened the constraint to cover roughly Laravel 5.8 through Laravel 7, and that is the whole supported envelope. Laravel 7 is itself end-of-life and several major versions behind current Laravel, so the package cannot be installed on a modern app without overriding Composer constraints. Even on the versions it lists, you still had to add the Inertia server adapter and npm client packages yourself.
- Is laravel-frontend-presets/inertiajs still maintained?
- No. The release cadence stalled in 2020, and the 0.4.0 changelog contains a single Laravel 7 compatibility item with no feature work, dependency modernization, or follow-up releases. There is no evidence of sustained upstream triage, so treat it as abandoned scaffolding rather than a dependency you can rely on. Pinned tooling such as webpack, Babel, node-sass, and Vue 2 or React 16 remains frozen at 2020-era versions.
- Do I still need inertiajs/inertia-laravel if I use this preset?
- Yes. The preset only bootstraps the client side and some server wiring; it does not replace the official Inertia server adapter. Teams still had to require inertiajs/inertia-laravel and install the matching npm client package themselves. That means the preset saves less effort than it appears to, since the core Inertia integration was always a separate, first-party install.
- What is the best alternative to this preset for Inertia in Laravel?
- Use the official route: require inertiajs/inertia-laravel, install @inertiajs/vue3 or @inertiajs/react, and then either scaffold with Laravel Breeze in its Inertia flavor, use Jetstream, or follow the Inertia docs for manual setup of the middleware, root Blade view, and Vite config. Those paths are first-party maintained, Vite-based, and current with Inertia v1 and v2. If a legacy app already uses this preset, port the generated files into that modern structure instead of reinstalling the package.
- Does this preset support Vue 3, React 18, or TypeScript?
- No. Its Node side references the pre-v1 @inertiajs/inertia packages alongside Vue 2.x and React 16 pins, so none of the modern frontend stacks are covered. There is no Vue 3, React 18, or TypeScript support in the generated scaffolding, and no release after 0.4.0 changes that. Porting the stubs to a current stack means rewriting most of the frontend config anyway.
- Does the preset use Vite or Laravel Mix?
- It generates a Laravel Mix and webpack setup, not Vite. Modern Laravel applications ship with Vite by default, so the generated build config will not drop into a Laravel 9 or later app without significant rework. You would need to rewrite webpack.mix.js, the package.json scripts, and the Blade asset directives to match a Vite pipeline.
- What does the preset actually scaffold in a fresh Laravel app?
- It injects the Inertia client and server setup, authentication controllers and views, layout components, and a set of example pages, plus asset pipeline configuration. The goal was to let you skip manual wiring and start building a single-page app with Laravel as the backend and Vue or React on the frontend. Because it also lays down webpack and package.json scaffolding, the generated files are tightly coupled to the 2020-era toolchain it was written for.
- Is it safe to use in production, or will it cause dependency conflicts?
- Installing it on a current stack is a cleanup burden rather than a risk-free convenience. The pinned webpack, Babel, node-sass, and Vue 2 or React 16 dependencies conflict with modern Composer and npm resolutions and carry transitive dev-dependency security findings from that older toolchain. Since it is a one-time scaffolding preset rather than a runtime library, the realistic recommendation is not to install it at all and instead use the official Inertia setup.
- How does it compare to Laravel Breeze or Jetstream with Inertia?
- Breeze and Jetstream are first-party, actively maintained starter kits that ship Inertia support with Vite, Vue 3 or React 18, and current Inertia versions, while this preset is a third-party scaffolding tool frozen at Laravel 7 and webpack. Breeze is the lighter option and is easy to customize, while Jetstream adds teams, API tokens, and other opinionated features on top. For any new Laravel project, either one replaces this preset entirely.
Weaver
How can I help you explore Laravel packages today?