Closed ThangHuuVu closed 1 month ago
We are experiencing the same issues. The error stack provides very little insight on what the root cause is. @leerob can we get some eyes on this please 🙏🏼 ? This is a show stopper for us in multiple projects. Not being able to use --turbo
slows development down quite drastically.
i'm facing the same issue with next@14.2.4
, next-auth@^5.0.0-beta.20
and turbopack
Same here.
Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!
This issue was resolved in v14.3.0-canary.81.
Should be fixed in https://github.com/nextauthjs/next-auth/pull/11551
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
Link to the code that reproduces this issue
https://github.com/ThangHuuVu/na-10585
To Reproduce
pnpm i
http://localhost:3000
Current vs. Expected behavior
Current: The error in the console:
Provide environment information
Which area(s) are affected? (Select all that apply)
Turbopack
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
I tested my reproduction against the latest canary
Removing
--turbo
flag will make it work again.