Sveltekit docs referers to NextAuth in some places.

[gerhardcit]

What is the improvement or update you wish to see?

This is the sample provided with sveltekit selected.

export const { handlers, auth, signIn, signOut } = NextAuth({
  callbacks: {
    async signIn({ account, profile }) {
      if (account.provider === "google") {
        return profile.email_verified && profile.email.endsWith("@example.com")
      }
      return true // Do different verification for other providers that don't have `email_verified`
    },
  },
})

Is there any context that might help us understand?

https://authjs.dev/getting-started/providers/google#configuration
has a selection for Next.js, Sveltekit and Express

if you change that, you would expect the rest of the page to adjust it's examples to that.

Does the docs page already exist? Please link to it.

https://authjs.dev/getting-started/providers/google#email-verified

[ndom91]

This is kind of by design. Ideally we'd have every single code example on the site be dynamic, but currently only the ones which exlicitly have the framework tabs change (and do sync with one another).

The configuration object between the different frameworks is identical though so it shouldn't be very challenging to see how one example fits for sveltekit, for example, in the case where it may be missing an explicit tab framework switcher.

[ndom91]

Thanks for your interest though. If yuo'd like to contribute more code examples for the various framework's we'd be happy about any PR's 😊