-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am getting error when trying to signin with next-auth #7466
Comments
I found the solution though it is not a problem with next-auth. I am posting this for future reference so it can help other folks. The problem was that I was running the build using turbo, I solved it by not using turbo as my build tool |
Why is this closed, i dont understand, it seems its been closed too quickly, this is a very serious issue. Yes it happens when yarn dev --turbo is used on nextjs, but the issue is clearly pointing to modules in next-auth, specifically node_modules/next-auth/node_modules/uuid/dist/esm-browser/v4.js:6:51 please take time to check this out before quickly closing it as completed. its an issue with UUID, take a look here |
can this issue be re-opened please, it seems the uuid version needs an update |
it doesn't look like this serious issue is not being attended to, its been 2 weeks now, the issue reporter mentioned he or she could help, but this is still closed and not being worked on, can we get an update on this please. |
Based on the comment by @dayemsiddiqui and what I also had to do to solve the same issue is that using turbo pack in your dev environment is likely causing this error. Navigate to your "scripts": {
"dev": "next dev --turbo",
} change it to "scripts": {
"dev": "next dev",
} |
Question 馃挰
Hi I have the following code:
And my env as follows:
And I am getting the following error whenever I try to signin:
Node version: 18
How to reproduce 鈽曪笍
Run the code above and you should see the error.
Node version: 18
OS: MacOS
Contributing 馃檶馃徑
Yes, I am willing to help answer this question in a PR
The text was updated successfully, but these errors were encountered: