Closed zwhitchcox closed 1 year ago
Ok, this was hard to find, but there's a guide on upgrading to V5 that I guess we're supposed to use?
And looking at the npm repo, there's a version 0.0.0-manual.83c4ebd1, which I guess is the build from feat/nextjs-auth
branch that I guess we're supposed to use as well?
It was quite hard to find both of these, so that's why I'm not sure...still better than building from source.
Ok, this is the only working example of next-auth v5 I've found that's fully functional, that I intend to copy.
It's using all the things I've mentioned, plus next.js canary. I think it's a good project to emulate:
cc @Yedidya10
Ok, this is the only working example of next-auth v5 I've found that's fully functional, that I intend to copy.
It's using all the things I've mentioned, plus next.js canary. I think it's a good project to emulate:
Still looking for an example with Suspense and Next-auth v5 haha.
Description 📓
Regarding #7953, it looks like the
feat/nextjs-auth
branch is necessary to use the App Router, which is the default recommendation of NextJS.It might be helpful for that branch should be published so we can use the recommended feature, or could you provide some clarity on how we should use this repo in coordination with NextJS? Unless you guys are not coordinating the repos together?
How to reproduce ☕️
Following the examples at
https://github.com/nextauthjs/next-auth/tree/790f7617083d055b94d05c5c815749258da84852/apps/examples/nextjs
and https://github.com/nextauthjs/next-auth/tree/790f7617083d055b94d05c5c815749258da84852/apps/dev/nextjs
I get the errors:
and
Contributing 🙌🏽
Yes, I am willing to help implement this feature in a PR