Jetstream Inertia Generator Laravel Package

Product Decisions This Supports

• Release scoping and estimation: The generator turns an admin CRUD module — migration, model, resource controller, form requests, routes, and Vue pages — into a single Artisan command. For roadmap work, that shifts internal-tool and account-surface estimates from weeks to days, which changes what fits in a release rather than just how fast it ships. Use it to re-baseline, then sanity-check against a hand-built module before committing the number.
• Stack selection: Livewire/Blade vs. Inertia SPA: Teams already on Jetstream can adopt the Inertia/Vue page tree without hand-writing auth, profile, and team screens. This reframes "move to Inertia" from a rewrite project into a line item in a stack-selection conversation — the cheapest experiment available if you want evidence before committing to a front-end architecture.
• Build vs. buy for internal scaffolding: It substitutes for an in-house CRUD generator. The trade isn't license cost (MIT, free) — it's ownership. You take on a small community maintainer in exchange for speed, and every generated file becomes your source of truth from the first commit. That is a governance decision as much as a velocity one, and it should be made explicitly rather than by default.
• Standardization across teams: Publishing customized stubs lets you codify house conventions once and generate consistent modules thereafter. That is a platform-consistency play with compounding returns — but it only pays off if adoption is deliberate (shared stubs, pinned version, named owner) rather than ad hoc per team.
• Roadmap risk signal: v3.4.0 is pure maintenance — a funding file plus Inertia, Laravel Vite, and Laravel dependency bumps. No features, no breaking changes. Practically: safe to adopt at a pinned version, but plan nothing that depends on upstream momentum. With zero dependents and a low opportunity score, treat it as a niche tool that stays niche.

When to Consider This Package

Consider it when:

• You are on Laravel + Jetstream and want the Inertia.js (Vue) variants of auth, profile, and team pages without hand-writing them — or need a fast admin panel, internal dashboard, or MVP surface.
• You are greenfield or adding a new module to a stock Jetstream app. The generator assumes unmodified Jetstream views, so prior manual edits are at risk.
• You can absorb the review cost: a disposable branch or spike app, immediate commit for diff review, and a pinned version are prerequisites, not optional extras.
• You have a named owner fluent in Laravel, Jetstream, Inertia, and Vite who will own the generated code and the upgrade path.
• The output is plain Laravel/Vue you already understand — meaning the downside if the project is abandoned is a bounded maintenance cost, not a rewrite.

Look elsewhere when:

• You are not on Jetstream, or you run an API-only Laravel service — the package adds nothing.
• You want a full admin-panel framework (Filament, Nova) rather than page scaffolding; that is a different buy decision with different support terms.
• You need vendor support, an SLA, or a published compatibility matrix. v3.4.0 ships none of these.
• Your Inertia pages, vite.config.js, or Tailwind setup are already customized — retrofit becomes a cherry-pick exercise, not an install, and should be estimated as an evaluation, not a quick win.
• Your Laravel/Inertia/Vite versions are pinned to older majors. The v3.4.0 dependency bump likely improved alignment with current versions while silently narrowing the supported range.

How to Pitch It (Stakeholders)

For executives: This is a free, MIT-licensed accelerator for Laravel teams that removes repetitive page-building work on admin, account, and internal-tool surfaces. It shortens time-to-market on internal tools and MVPs, and every line it generates lands in our repository as ordinary source we control. The costs are indirect: no vendor support, a single-maintainer project with no dependent packages in the wild, and an undocumented version-compatibility surface we would have to validate ourselves. Recommendation: fund a one-week, single-module pilot, measure hours saved against hand-built pages, and let that data decide broader adoption. Do not make it a platform dependency on the strength of a demo — the blast radius is small, but so is the evidence.

For engineering: Install it as a Composer --dev dependency on a disposable Jetstream/Inertia branch, pin v3.4.0, publish the config and stubs, and generate one representative module end to end. Validate the Laravel, Jetstream, Inertia, Vite, and Node version matrix first — the release notes only say dependencies were updated. Commit immediately after generation to create a reviewable diff and a rollback point. Confirm the generated pages build and render styled; the most common false alarm is a Tailwind content glob that omits resources/js/**. Then set policy: generated files are committed and customized only after generation is accepted, and are never bulk-regenerated over customizations. Treat it as a productivity tool, not a framework — low ramp-up for anyone already fluent in Jetstream and Vite, medium for teams new to Inertia who will misattribute toolchain misconfiguration to package bugs.