bug: next-auth module completely broken with MODULE_NOT_FOUND next/server.js when doing folder structure instead of app

[marcomnrq]

Provide environment information

Happening in the latest version available: [email protected].

Describe the bug

On public and protected routes, the tRPC calls made from the client fail indicating the following error:

 Error: Failed to load external module next-auth: Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Users/marcomnrq/VSCode Projects/examplebug/node_modules/next/server' imported from /Users/marcomnrq/VSCode Projects/examplebug/node_modules/next-auth/lib/env.js
Did you mean to import "next/server.js"?

Reproduction repo

n/a

To reproduce

Create a new app using the following settings.

Start the app with npm run dev and see the console / logs.

Additional information

Happy to help debugging this further, but i think it has to do with the import in this file. Will try to post some findings in this issue.

[marcomnrq]

This looks to be related > vercel/next.js#64529

[visheshd]

Getting this with our codebase as well. Just tried to update to the latest t3-boilerplate.

[BrentonBeltrami]

This is related/duplicate of #2027.
I am also getting this error.

[ari-party]

nextauthjs/next-auth#9385 (comment)

[timmatsam]

Also getting this error - I feel as if it wasn't prudent to update next-auth to the beta version - i'm a bit surprised a non stable version was approved into the t3 app? Was playing around with this to no avail, mapping next-auth to the transpilePackages option in the next config file did not fix it for me as per ari-party's reference. Best thing to do is to use the 7.37.0 version until a fix has been implemented.