Closed 0xHorace closed 9 months ago
Using the canary version of Next 13.4.7-canary.1
and next-auth 0.0.0-manual.83c4ebd1
it seems to work. Changing either of these breaks it.
I was able to upgrade nextjs and next-auth by moving away from middleware https://github.com/nextauthjs/next-auth/issues/7732
Using the canary version of Next
13.4.7-canary.1
and next-auth0.0.0-manual.83c4ebd1
it seems to work. Changing either of these breaks it.
At first I thought I needed to patch oidc-token-hash in addition to using these release candidates, but it really only required using these versions, thank you.
The fact that you have to use canary/hacked versions of the two foundational dependencies makes this template a lot less useful for building production apps.
@shadcn help us! <3
next-auth@beta & next 14 seems to be working, still not 100% done migrating though
This is my commit migrating to Next 14.0.2 and Next Auth 5 Beta: https://github.com/vercel-labs/ai-chatbot/commit/054c26d32e100dae5983ebd2970d9e86eb84dfb0
Updated to all latest versions, including Next.js and NextAuth.js here: https://github.com/vercel-labs/ai-chatbot/pull/186
I have been hacking a project based on this repo and found workarounds with the version of next-auth that's implemented even though it is not the latest. Some roadblocks I've encountered is that the
credentials
next-auth provider won't work because of thestream
package, themongodb
adapter doesn't work in next-auth options, and I can't use the next-authgetServerSession()
function.I've recently tried again to troubleshoot upgrading to the latest next-auth with this repo and here's what I did and what Im encountering:
"next-auth": "0.0.0-manual.83c4ebd1"
rm -rf node_modules & rm pnpm-lock.yaml
pnpm add next-auth@latest
pnpm install
when I
pnpm run dev
I encounter this error:the contents of the
oidc-token-hash
file:attempt at implementing fallback logic:
returns a new error:
From here I am stuck, a little hesitant to keep digging and making changes to these dependencies. Hopefully this at least provides someone else with a similar issue some insight as I've seen some other issues related to next-auth. Any help would be greatly appreciated, as well.