Weave Code
Jetstream Inertia Generator Laravel Package
savannabits/jetstream-inertia-generator
A Laravel scaffolding tool that generates Jetstream Inertia CRUD pages—Vue components, controllers, models, routes, and forms—from your database tables. Ideal for quickly building admin panels and dashboards.
Admin CRUD generator using Laravel Jetstream, Inertiajs, Vue.js, Pagetables and Tailwindcss
Frequently asked questions about Jetstream Inertia Generator
- What does savannabits/jetstream-inertia-generator actually do?
- It is a development-time scaffolding tool that reads your database tables and generates Jetstream Inertia CRUD pages: Vue components, controllers, models, routes, forms, layouts, middleware and provider bindings wired the way Jetstream already expects. It targets admin panels, dashboards and repetitive internal CRUD surfaces rather than API-only or Blade/Livewire applications. It is not a runtime dependency, so it never belongs in a production manifest.
- Which Laravel, Jetstream, Inertia and Vue versions are supported?
- There is no published support matrix; the only compatibility signal is the v3.4.0 dependency bump covering Inertia, Laravel Vite and Laravel, which likely aligns with current majors while quietly narrowing support for older ones. Confirm PHP, Laravel, Jetstream, Inertia, Vite and Node versions by experiment: Composer constraints, npm peer dependencies, a clean npm install and a production frontend build. Treat any version claim as unverified until your own spike app proves it.
- How do I install and configure the package in a Laravel app?
- Install it with Composer as a dev dependency inside a Laravel application already scaffolded with Jetstream using the Inertia and Vue stack plus Tailwind, then run the package's generator command against a database table. Note the naming mismatch: Composer lists savannabits/jetstream-inertia-generator while the repository lives under coolsam726, so record both names in procurement, allow-lists and your internal registry to prevent duplicate adoption. Retrofit effort is medium to high because the generator writes into files teams typically own, such as route files, app.js, vite.config.js and Tailwind config.
- Does the generator overwrite existing files, or is it idempotent?
- Idempotency is not documented, so assume the generator can skip, prompt or overwrite unpredictably and plan accordingly. Because its output path includes route files, the application bootstrap, Vite and Tailwind configuration, always run it on a feature branch or a disposable spike app and review the diff before committing. Regeneration after an upgrade risks clobbering local customisations, which is a recurring maintenance tax rather than a one-time cost.
- Is it safe to use in production?
- It is a development-time scaffolding accelerator, not a runtime dependency, so it belongs in require-dev and should never appear in a production manifest. The files it emits—Vue pages, controllers, models, routes and forms—become ordinary team-owned source the moment you commit them, so review, test and maintain them like hand-written code. The tool changes how fast your team ships, not what the system runs.
- Can I use it with Livewire, Blade, or React instead of Vue?
- Vue is the primary and best-supported target; React support is nominal at best, and the generator is a poor fit for API-only services, Livewire or Blade shops, or front ends where Inertia pages, vite.config.js and Tailwind config are already heavily customised. For a team currently on Jetstream's Livewire stack, adopting this package is a stack-migration experiment and must be estimated as one—the package only removes the front-end page-writing portion of that work. Validate any React path yourself rather than assuming parity with Vue.
- Does it honour Jetstream feature flags like teams, API tokens and SSR?
- This is unverified and explicitly flagged as an open question: whether the generator respects Jetstream feature flags such as teams, API tokens and SSR, and whether it handles both Vue and React paths, is not documented. Test each flag combination in a spike app before relying on it for real modules. Also check whether a separate SSR build succeeds with the generated page tree and bootstrap wiring.
- What is the maintenance status, and what happens if the package is abandoned?
- It is a single-maintainer, MIT-licensed community package with zero dependents, a low score and no commercial support path, so abandonment is a realistic scenario. The blast radius is bounded because the generated output is plain Laravel and Vue your team already owns and can maintain without the tool. Check maintainer responsiveness on issues and pull requests over the last 90 days, and treat command signature stability—how often the generator command changes across minor releases—as a semver risk.
- What are the alternatives to this CRUD generator?
- The practical alternatives are writing the Jetstream Inertia pages by hand, staying on Jetstream's Livewire stack, or evaluating a different admin panel or CRUD generator against your exact Laravel, Inertia, Vue and Vite matrix. No drop-in equivalent is documented in this package, so compare candidates on the same spike-app criteria rather than on feature lists. For small projects, hand-writing the first module is often cheaper than absorbing an undocumented compatibility investigation.
- How should I evaluate the package before adopting it?
- Stand up a disposable Jetstream and Inertia spike app or a feature branch, pin v3.4.0, generate one representative resource and diff the output against your house conventions. A small diff justifies adoption for new modules only; a large diff means porting selectively—take the Pages tree and application bootstrap while keeping your own Vite, Tailwind and route files. This pilot generates the evidence the package itself does not provide: a supported version matrix, a clean npm install, a production frontend build and an SSR build.
Weaver
How can I help you explore Laravel packages today?