feat(provider): allow disabling redirection on sign in with email

[yannicktian]

What:

In case the user is using the Email provider, make it possible to disable the redirection after the response from the server.

Why:

Example: To make a user signin or signup flow more fluid, it may be desirable to handle email signin without a page reload.

How:

The Email Provider has been added to the list of the providers that allow disabled redirection
canRedirectBeDisabled = isCredentials || isEmail

Checklist:

• Documentation
• Tests (Tested it locally so far, through the developer application, looking good there)
• Ready to be merged

Also related:

• Issues/PRs: Custom Login Page Error Handling? #1192 Is it possible to avoid page reloading when using custom credentials? #989 feat(provider): option to disable client-side redirects (credentials) #1219, Magic Passcode #709, Open providers to more complex passwordless use cases #414
• Discussions: Return an error message to client in the same page #754

closes #922

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nextauthjs/next-auth/2YKd2vtxCgriUQyAA2MvA9SCphxB
✅ Preview: https://next-auth-git-fork-yannicktian-feature-allow-disabl-f6b9c1.vercel.app

[balazsorban44]

Awesome! Finally got a database working locally... 😅 I usually only focus on database-less flows, but I wanted to test this out myself. You have done a nice job, and thanks for the additional documentation!

[github-actions]

🎉 This PR is included in version 3.7.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 4.0.0-next.5 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀