Nico Domino

@CyanFlare @sjoukedv I think both of these are due to an issue we had with `AUTH_URL`/`basePath`. This shuold be fixed in `main` I believe, unfortunately we haven't cut a release...

@MrOxMasTer Hmm so it's working "as expected" with `AuthError`, but when yuo extend it from `CredentialsSignin` you get this odd next/fonts error, did I understand that correctly?

@MrOxMasTer Was just trying something with this again in `beta.16` and wanted to report that the above did work for me with `import { CredentialsSignin } from 'next-auth'`, but with...

All `@auth/*` packages are ESM-only. We realize this may be a bit bigger of an issue with the express package as compared to the other (browser-only) ones. To fix it,...

Small type / slot updates to SvelteKit server-side `SignIn` / `SignOut` components here: https://github.com/nextauthjs/next-auth/pull/10144

Sorry but we're shipping new docs shortly and this change is already in, I'm going to close this PR :pray:

> But with `adapter: PrismaAdapter(prisma)` when I move the `callbacks: {...}` from `auth.ts` to `auth.config.ts` I got the error `[auth][cause]: Error: PrismaClient is unable to run in Vercel Edge Functions...

@AmphibianDev ah okay, no so only if you're running on an edge runtime then Prisma has issues, although they can be worked around like implied by Thang and ConnorC18 detailed....

Also quick note, Prisma is beginning to release edge compatible clients. In their latest `5.9.1` release they already updated it to not throw when imported in an edge runtime, but...

Yeah so historically the only option has been Prisma Accelarate. This is just a db connection pooler behind an HTTP endpoint, so you all you needed was an http client...