- How do I install the nunomaduro laravel-starter-kit-inertia-vue?
- You scaffold it rather than require it. Use composer create-project nunomaduro/laravel-starter-kit-inertia-vue, the laravel new installer where available, or clone the repository and fork it as your own baseline. It is an opinionated application skeleton, not a library you add to an existing composer.json with composer require.
- Can I use this starter kit in an existing Laravel application?
- Not directly. It is designed for greenfield or near-greenfield projects, and introducing its structure into an existing app would create a parallel architecture. The practical approach is to treat it as a reference and port specific conventions such as the Action pattern, Fortify configuration, strict types, Pest, Pint, Larastan, and Rector selectively behind a CI gate.
- What PHP and Laravel versions does this starter kit require?
- The kit targets a forward-looking matrix: PHP 8.5, Laravel 13, Inertia v3, and Pest v5. It also pulls in pre-1.0 dependencies including Wayfinder v0, MCP v0, and Prompts v0. Check that your hosting, CI runners, and container base images support PHP 8.5 before committing, since some environments lag behind.
- Which frontend stack does this starter kit use?
- It pairs Laravel with Inertia.js v3 and Vue, giving you an SPA-style application without building a separate API. You will need a Node and Vite build toolchain plus a matching @inertiajs/vue3 client version. Note that Inertia v3 itself is a breaking surface, with changes such as Axios removal and the replacement of Inertia::lazy() with optional().
- What authentication does this Laravel starter kit ship with?
- Authentication is handled by Laravel Fortify, giving you a session-based auth backend out of the box. It does not include SSO, Socialite, or Passport, so if your identity model depends on those you will need to add them yourself. Teams with enterprise identity requirements should evaluate that gap before adopting the kit.
- What testing and code quality tools are included?
- The kit ships with Pest for testing, Larastan for static analysis, Pint for formatting, and Rector for automated refactoring. It also includes Laravel Boost and MCP guidelines plus AGENTS.md files with AI-agent operating instructions and skill activation rules. If your team does not use Boost or MCP tooling, those files are harmless but unused.
- Do I need to run wayfinder:generate in my build pipeline?
- Yes. Wayfinder generates route helpers that the frontend imports depend on, so the wayfinder:generate step must run as part of your build and CI pipeline. Treating it as a local developer ritual will produce broken frontend builds or stale imports. Pin the Wayfinder version in your fork and confirm the generated output is reproducible.
- Is this starter kit production-ready, or should I wait for stable versions?
- It is intended to be forked and owned rather than consumed as a versioned dependency, so there is no semantic-versioning contract or upstream merge guarantee. The aggressive version matrix means every future upgrade is a manual reconciliation, and the project has a single maintainer with modest adoption. Pin and lock the full dependency matrix, record the upstream commit SHA as your baseline, and treat abandonment risk as a foundation-layer decision.
- How do I keep my forked starter kit in sync with upstream changes?
- Immediately re-point origin to your own repository and add the upstream as a read-only remote. Record the upstream commit SHA you forked from as your baseline and document a cherry-pick policy before feature work begins. Because there is no upstream merge guarantee, plan for manual reconciliation rather than assuming clean updates.
- How does this compare to Laravel Breeze, Jetstream, or other starter kits?
- The main differentiator is the committed Inertia v3 plus Vue SPA stack with Fortify, Wayfinder route generation, and an Action-pattern convention enforced alongside Pest, Larastan, Pint, and Rector. Breeze and Jetstream offer different frontend and auth combinations and are generally more conservative on version requirements. If your team has not committed to Vue with Inertia, or your hosting cannot support PHP 8.5 and Laravel 13 today, a more established starter kit is the lower-risk choice.