Hey! 👋

I've been testing for the past 8 hours on how to implement Next-Auth using Mongoose (credentials provider). However, I've noticed there are numerous compatibility issues (like being forced to implement NextAuth as a route) and implementation variations (different API Structures, Calls etc).

I wanted to ask if someone would be so kind as to help me implement missing features and fix my template while still keeping it kinda in the same schema.

My template includes a simple main page, login, register, and dashboard (in JavaScript, not TypeScript).

Currently, I'm facing the following issues:
- Despite renaming the user saved in the database, NextAuth still thinks I'm logged in and considers it valid.
- I have concerns about the way I've implemented NextAuth.
- Understanding in how to correctly implement checking whether the User is logged in and valid. (ServerSideProps?)

With "missing features", I meant possible security concerns.

This is my first time using NextAuth and I'm also kind of new to NextJS (Only made some small projects), so it would be amazing if anyone could help me refine my template and teach me where I might be going wrong.
I will most likely later once I feel like it's completed publish it to GitHub, since I couldn't find anything that matches the latest standards and has a good structure.

The best I could find was:
https://github.com/Parth731/nextjs-credentials/tree/master
https://github.com/spruceid/siwe-next-auth-example/tree/main (Javascript Implementation and outdated)
https://github.com/vercel/next.js/tree/canary/examples/with-mongodb-mongoose (not a NextAuth implementation)