feat: support advanced initialization in v5

[ThangHuuVu]

☕️ Reasoning

Add support for advanced initialization for v5.

🧢 Checklist

• Documentation
• Tests
• Ready to be merged

🎫 Affected issues

Fixes: #9455

📌 Resources

• Security guidelines
• Contributing guidelines
• Code of conduct
• Contributing to Open Source

[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	Jan 16, 2024 8:16pm

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
next-auth-docs	⬜️ Ignored (Inspect)	Visit Preview		Jan 16, 2024 8:16pm

[chrisivo]

Is there any way lazy initialisation can be executed asynchronously? I need to make async calls to obtain the Id's and secrets for the providers. I could do this using v4, but seems like there's no support in v5 beta (so far)?

[ndom91]

@chrisivo what do you mean exactly? The first argument to NextAuth() can be an async function. So yuo can do this (as is shown in most examples):

export const { auth, signIn, signOut } = NextAuth({
  providers: [ ... ],
  debug: true
})

But yuo can also do this:

export const { auth, signIn, signOut } = NextAuth(async (req) => {
  return {
    providers: [ ... ],
    debug: true
  }
))

EDIT: Sorry, just double checked and this seems to only be the case for the SvelteKit client. next-auth only seems to take synchronous functions as an alternative 🙏

[chrisivo]

Thanks for the response @ndom91.

Is there any roadmap at all for introducing asynchronous functions when initialising in next-auth ?