Jetstream Stack Change From Livewire to Inertia After Installation

Answer

No. Changing stack in config/jetstream.php from livewire to inertia does not activate Inertia routes, controllers, or views after installation. Jetstream treats that value as installer input, not a runtime toggle. You must remove or replace the Livewire frontend scaffolding, install Inertia scaffolding, and rebuild assets.

Confirmed facts

The stack key records which frontend the installer configured. Fortify authentication routes are stack-agnostic, so login and registration endpoints keep working, but each stack renders its own views. Feature flags such as two-factor authentication and API tokens can remain enabled in config/jetstream.php, yet they must match the UI that actually renders them; otherwise Fortify may expose routes with no matching stack view.

Steps for this case

1. Back up the application, preferably with a clean Git commit, before removing any frontend files.
2. Confirm installed versions with read-only commands:

   composer show laravel/jetstream
   php artisan --version

   Compare those versions against the Jetstream release notes for your series. Inertia support and asset tooling, such as Vite versus Laravel Mix, depend on the installed Jetstream and Laravel releases.
3. Inspect the installer before running it: php artisan jetstream:install inertia --dry-run if available for your Jetstream version, or read the installer source in vendor/laravel/jetstream to see which files it publishes.
4. Remove Livewire-specific scaffolding, including views, components, and any Livewire route bindings, then install Inertia scaffolding, typically php artisan jetstream:install inertia. Add --teams only if your app uses Jetstream teams.
5. Install and rebuild frontend assets: npm install, then npm run build. Use npm run dev for local development.
6. Align Fortify features: confirm config/jetstream.php features and Fortify feature flags match the enabled Jetstream features, then test login, registration, dashboard, and profile pages.

Verification after the swap

• Search for remaining Livewire references; their absence plus Inertia page files indicates the frontend changed.
• Confirm routes/fortify.php and config/jetstream.php feature flags are consistent.
• Run the asset build without errors and exercise the authentication flows.

Missing diagnostic detail

Provide the output of composer show laravel/jetstream and php artisan --version. The Jetstream version determines whether jetstream:install inertia is supported and which build tool the scaffold expects, so this detail changes the recommendation.

Assumptions and uncertainty

• This assumes a standard Jetstream and Fortify installation without a custom Fortify service provider or heavily customized authentication controllers.
• Running jetstream:install inertia on an existing app may duplicate or conflict with installed scaffolding; inspect installer actions for your Jetstream version before proceeding.
• Exact file paths and installer flags vary by Jetstream release; treat version-specific steps as requiring review.

This draft requires human verification against your installed Jetstream release notes before running destructive or scaffold-modifying commands.