Laravel Jetstream is a beautifully designed application scaffolding for Laravel.

This PR adds optional support for Laravel Socialite and all Socialite support providers, via feature flags. Support is available for both InertiaJS and Livewire. See #214

To get started with this PR, create a fresh Laravel project (without --jet) and update your composer.json to include the repository following and require the feature branch.

composer require laravel/jetstream:dev-feature-jetstream-support

You may then run the Jetstream install command, specifying socialite support:

php artisan jetstream:install {stack} --socialite

You may remove support for Socialite by commenting out the feature in jetstream.php

'features' => [
    // Features::socialite(['facebook' => true, 'github' => true]),
],

You'll need to follow the instructions for configuring socialite providers to ensure you're application will support this feature.

Once you're all setup, you should be able to see your providers in your login and register routes views:

Existing users that have signed up using email and password can connect social accounts in their profile settings, as well as remove them:

Besides normal login and two-factor, it might be nice to add OAuth login. Because Socialite is a first-party package, this could make sense to add by default.

Ideas:

• Configure socialite providers, eg Google, Facebook etc
• Register with Socialite (define the fields)
• ~Whitelist~ Allowlist registration for certain domains (eg. let everyone inside the company register, nobody else)
• Login with Socialite (perhaps optionally disable normal login)
• Connect/disconnect your account with other accounts on your profile page
• Possibility to skip 2FA if coming from Socialite (because other accounts could handle it)

What would be needed

• Additional table with socialite ids
• UI for login/connect/register
• Registering of socialite / mapping of fields

• Jetstream Version: 1.0
• Laravel Version: 8.0
• PHP Version: 7.4.3
• Database Driver & Version: MySQL 5.7
• Node version: latest

Description:

After installing using the new Laravel installer, data is not being reflected in the UI for /user/profile

After publishing all Jetstream assets I tried to see where this may be happening but it wasn't clear. However, I am getting the console error: Uncaught ReferenceError: Livewire is not defined at profile:626. All npm assets have been installed and everything else, including dropdowns and registration works.

If it helps in anyway, I am also using Vessel for a docker environment at the moment, and that is using version: 5.0

Steps To Reproduce:

• Create a new Laravel install: laravel new app --jet --stack=livewire
• cd app
• npm i
• Register a new user
• Open console and error is displayed.

If you enable 2FA and "forget" to scan the QR code, the user can't login anymore :)

Normal after you scan your 2FA code you have to enter it again on the page before the two_factor_secret is saved into the user model, this way you kinda ensure you registered your login in your 2FA application.

Solves #326

This PR automatically publishes and registers the new HandleInertiaRequests Inertia Middleware with the Http Kernel, to enable automatic asset versioning (cache busting) and error sharing as of default. To take full advantage of this, it also enables versioning as of default in the webpack.mix.js.

Additionally, because Jetstream automatically registers the ShareInertiaData middleware on the 'web' group as priority middleware, this PR also adds logic to ensure the HandleInertiaRequests middleware always runs directly after it when it exists. This gives the user the ability to overwrite the Inertia built-in defaults (such as the user key) if they want to.

Finally, because this Middleware will exist entirely in userland, it allows the user to change it in to any configuration they want, including disabling it entirely.

The Inertia stack is using a session var based workflow to determine if the user has started confirming two factor auth activation. If the user aborts confirming the two factor activation, for example by reloading the page, the two factor model-attributes are being reset accordingly. Such as two_factor_secret and others, which is working fine in the current implementation.

But, on every /user/profile visit or refresh the two factor model-attributes are reset causing unnecessary database updates, and also causing for example re-indexing of the whole model when Laravel scout is used, as long as two factor is not activated. This is because the current implementation does not check if the two factor confirmation has truly started.

With this PR the session variable 'two_factor_confirming_at' is being checked if present in the 'neverFinishedConfirmingTwoFactorAuthentication' method, resulting two factor model-attributes resets only if the two factor auth activation has been started by the user. If the user has not started the two factor auth activation, then the model-attributes are not reset.

The livewire stack is not using a session based workflow which is the reason why there are no updates and test required.

• Changing $page.user to $page.auth.user makes authenticated user consistent with intertia.js examples.
• Prevents mixing the auth.user with a user object returned from backend.

• Jetstream Version: 1.0.2
• Laravel Version: 8.0.1
• PHP Version: 7.4.7
• Database Driver & Version: mysql Ver 14.14 Distrib 5.7.29, for osx10.15
• Stack: Inertia

Description:

When the session expires the user doesn't get redirected to the login page, but instead this page is shown as a modal. After logging in within the modal the website is shown inside the modal.

Steps To Reproduce:

• Create a new Laravel + Jetstream project using laravel new saas --jet --stack=inertia --teams
• Register an account
• When logged in, open your preferred devtools and delete the laravel_session cookie
• Click on a link, for example in the user-dropdown click on "Profile"
• A modal is now shown with the login page
• When logging in within the modal the site will be displayed inside the modal

• Jetstream Version: 2.6.7
• Jetstream Stack: Inertia
• Uses Teams: no
• Laravel Version: 9.4.1
• PHP Version: 8.1.3
• Database Driver & Version: MySQL v8.0.28 for macos12.2 on arm64 (Homebrew)

Description:

Auth::login and Auth::loginUsingId causes user to be logged out

Steps To Reproduce:

• Install fresh copy of Laravel 9 w/ Jetstream + Inertia
• Create a route to switch users with Auth::login($user) or Auth::loginUsingId($id)
• Create 2 user accounts
• Log in as user 1
• Try using the route to login as user 2
• Return to the dashboard
• You are logged out instead of being logged in as the other user

https://github.com/fylzero/bug-report

• Jetstream Version: 1.6.5
• Jetstream Stack: Livewire
• Laravel Version: 8.20.1
• PHP Version: 7.3

I have troubles when installing Jetstream.

First:

composer require laravel/jetstream

This works as expected.

Then:

php artisan jetstream:install livewire

Output:

Migration created successfully!

ErrorException

file_get_contents(/Users/xxxx/xxxx/xxxx/xxxx.net/.env.example): failed to open stream: No such file or directory

at vendor/laravel/jetstream/src/Console/InstallCommand.php:516

Then I try to uninstall Jetstream:

composer remove laravel/jetstream

The uninstaller runs, at the end I see this output:

...

Generating optimized autoload files
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi

In fortify.php line 134:
                                          
Class 'Laravel\Fortify\Features' not found  
                                          
Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

This PR adds Inertia variants for all Jetstream included views. This allows a more native Inertia experience for users of this stack, and solves several issues and difficulties that makes for an all-in-all smoother experience.

For example, some Jetstream users have been asking questions on our Discord regarding difficulties they're experiencing with getting Jetstream to play well with Inertia. Specifically, the most common issue is when a session expires, as the user then gets redirected to the login page, and because that login page is a Blade view, Inertia renders it in a so-called 'error modal'.

To solve or prevent this, users should instead use Inertia for their login pages as well, and while some have gotten to the point where they're attempting to (re)configure Fortify to use Inertia views instead, this too isn't the most straight-forward thing to do.

This PR introduces opt-in dark mode support to Jetstream, borrowed from @jessarcher PR on Breeze

php artisan jetstream:install {stack} --dark

Following the previous mentioned PR, the dark mode classes will be stripped unless dark mode is enabled. When installing livewire stack without dark mode, the components will be published in order to strip the dark classes from them.

Screenshots

|Light|Dark| |-----|-----| ||| ||| ||| ||| ||| ||| ||| ||| ||| ||| ||| ||| ||| ||| ||| ||| ||| ||| ||| ||| ||| ||| |||

Notes

• I copied the styles of inputs & buttons from Breeze PR, which will change colors from blue to indigo, happy to change back all to blue if this presents a problem.
• I used Livewire stack as a basis and then copied to Vue, while doing this I found minor inconsistencies between the stacks which are now improved. This includes the caret icon in the user's dropdown and some minor visual differences - keep this in mind when reviewing the diff.
• I've included the fix focus styling in this and included the dark mode options.