fix(core): handle an error inside parseProviders() when providerId not found in config

[KostyaTretyak]

☕️ Reasoning

Currently, if an invalid providerId is entered, the parseProviders() function will return an empty provider. I discovered this when I intentionally entered an incorrect providerId in the url curl -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:

TypeError: Cannot read properties of undefined (reading 'type')

Error stack pointing to this row:

next-auth/packages/core/src/lib/index.ts

Line 73 in 6bd0f96

if (options.provider.type === "credentials")

🧢 Checklist

• Documentation
• Tests
• Ready to be merged

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
auth-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 30, 2024 11:05pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
next-auth-docs	⬜️ Ignored (Inspect)	Visit Preview		Dec 30, 2024 11:05pm

[vercel]

@KostyaTretyak is attempting to deploy a commit to the authjs Team on Vercel.

A member of the Team first needs to authorize it.

[balazsorban44]

Thanks, looks good! But maybe in a follow-up PR, could you add a custom error in here?: https://github.com/nextauthjs/next-auth/blob/main/packages/core/src/errors.ts

[KostyaTretyak]

Okay. I will try at the next opportunity.