fix(core): handle an error inside parseProviders() when providerId not found in config
#12438
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
|
@KostyaTretyak is attempting to deploy a commit to the authjs Team on Vercel. A member of the Team first needs to authorize it. |
…` not found in config.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
☕️ Reasoning
Currently, if an invalid
providerIdis entered, theparseProviders()function will return an emptyprovider. I discovered this when I intentionally entered an incorrectproviderIdin the urlcurl -iS http://0.0.0.0:3000/auth/callback/providerType -d ''so that the error handler would tell me what to enter. Instead, it throws the following error:Error stack pointing to this row:
next-auth/packages/core/src/lib/index.ts
Line 73 in 6bd0f96
🧢 Checklist