Nico Domino

Yeah thanks, so the idea was actually to provide another error class to extend for custom credentialErrors that **doesnt** extend `AuthError`, because that would end up with our messaging appended...

Thanks, this looks great! I made some tiny edits regarding the `loops.svg` image file. Could you update the svelte examples (in both mdx files) regarding the environment variables? Unfortunately SvelteKit...

Looks like there are still some TS issues [here](https://github.com/nextauthjs/next-auth/actions/runs/10603214620/job/29387015818?pr=11197) though

@Whats-A-MattR just wanted to simplify this a bit further as all those extra interfaces weren't necessary. Thanks for getting it back to building :pray:

Ah so after fixing some of the other build issues in the repo, it looks like there's still an issue with this PR / loops provider, see: https://github.com/nextauthjs/next-auth/actions/runs/10983054627/job/30492001767?pr=11197

> @ndom91 @ThangHuuVu @ubbe-xyz could we possibly do the thing now please? Please don't tag maintainers directly 🙏 Regarding getting this in, are the extra types you added back really...

@k-taro56 thanks for that big PR! I left a littel note there. After we cleanup the `42School` imports, etc. there though, we can continue in this PR with any required...

> Sure, happy to help! We've merged that PR, would love if you could clean this up and we can ship the rest of your 42school fixes 👍

Hmm, I think the wording is a bit strict. The credentials provider is useable without the jwt session strategy, but using the database session strategy doesn't auto generate accounts, users,...

The fields marked with `?` are the ones Prisma is showing you are available. It looks like you just had it in reverse order, i.e. `providerAccountId_provider` would have worked.