Skip to main content
Tutorial Free

How to Install JetStream in Laravel 12

February 27, 2025
1 min read

With Laravel 12, creating a new project doesn't show the option to install the JetStream starter kit, which you may want to use for features like 2FA or Teams that new kits don't have (yet). However, Jetstream is compatible with Laravel 12. Here's how to install it.

First, with the new Laravel installer, you only see the options for new starter kits.

Also, laravel new project --jetsream flag will not work in the new Installer.

In the screenshot above, you need to choose None and create a new Laravel project without any kit.

Next, you can install the Jetsream package via Composer.

composer require laravel/jetstream

Next, you run php artisan jetstream:install and you will see your familiar stack options to choose from.

After choosing your stack then, you can choose optional features like team support.

After visiting the home page, you can see a familiar welcome page with login and registration links.

After registering, you will see a familiar dashboard.

That's it. Jetstream is installed, and you can continue like you did with the older Laravel 11 version.

If you want the official documentation, Jetstream has a dedicated page.

Enjoyed This Tutorial?

Get access to all premium tutorials, video and text courses, and exclusive Laravel resources. Join our community of 10,000+ developers.

Recent Courses

Comments & Discussion

O
OXILYUM ✓ Link copied!

What about React with Inertia

N
Nerijus ✓ Link copied!

What about it? Jetstream never had react version

O
OXILYUM ✓ Link copied!

Yes I know, I ask this because Laravel now add a startki with react and I hope jetstream will be compatible with

N
Nerijus ✓ Link copied!

There will never be jetstream with react. Maybe someone made it, google it. Officialy won't happen

O
OXILYUM ✓ Link copied!

Never say never...

BA
Byron Ajila (HaNaTo) ✓ Link copied!

Hi, I've tried installing Jetstream on Laravel 12 using both the traditional method and the approach described here, but in both cases I encounter the following error:

npm error While resolving: undefined@undefined
npm error Found: vite@7.0.6
npm error node_modules/vite
npm error dev vite@"^7.0.4" from the root project
 
npm ERR! Could not resolve dependency:
npm ERR! peer vite@"^5.0.0 || ^6.0.0" from @vitejs/plugin-vue@5.2.4
npm ERR! node_modules/@vitejs/plugin-vue
npm ERR! dev @vitejs/plugin-vue@"^5.0.0" from the root project

Would it be safe to proceed using --legacy-peer-deps, or could this introduce compatibility issues later on?

N
Nerijus ✓ Link copied!

Manually bump @vitejs/plugin-vue version to ^6.0.0 and error will be gone.

We'd Love Your Feedback

Tell us what you like or what we can improve

Feel free to share anything you like or dislike about this page or the platform in general.