-
Notifications
You must be signed in to change notification settings - Fork 804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing personal team on fresh install #1460
Comments
Hi there. This isn't a Jetstream issue. You need to add |
@driesvints Thanks! What do you mean with "this isn't a Jetstream issue"? Jetstream introduces the Teams functionality, no? Currently anybody installing Jetstream (with teams support) on top of a fresh Laravel installation will inadvertently encounter this issue, leading to having to understand the error, google it, search GitHub issues, etc., basically individually having to figure out that Since Jetstream should only be installed on new Laravel applications only, this issue could very easily be remedied by copying an already working |
@miclaus if you could send in a PR that adds it to the seeder without too many workarounds we could maybe consider it 👍 |
Jetstream Version
5.0.0
Jetstream Stack
Inertia
Laravel Version
11.0.8
PHP Version
8.2.0
Database Driver & Version
No response
Description
When installing Jetstream (Inertia) with teams support, the example user created in
DatabaseSeeder.php
isn't created with a personal team which leads to a blank dashboard and the following error being logged to console forapp.js
when logging in with the test user[email protected]
:The following in
DatabaseSeeder.php
:Should be:
Related issue: #1341
I'm open to do a PR.
Steps To Reproduce
composer create-project laravel/laravel:^11.0 example-app
composer require laravel/jetstream
php artisan jetstream:install inertia --teams --ssr --dark
(--ssr
and--dark
might not be the issue here)npm install
npm run build
php artisan migrate
[email protected]:password
The dashboard is blank and error is logged in console.
The text was updated successfully, but these errors were encountered: