-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: next-auth module completely broken with MODULE_NOT_FOUND next/server.js when doing folder structure instead of app #2033
Comments
This looks to be related > vercel/next.js#64529 |
Getting this with our codebase as well. Just tried to update to the latest t3-boilerplate. |
This is related/duplicate of #2027. |
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 |
This worked for me nextauthjs/next-auth#10058 (comment) |
I encountered the same issue and attempted the following solutions to resolve it:
|
Simplest "fix" for this I've currently seen is to modify diff --git a/next.config.js b/next.config.js
index 080cc56..a5c18b9 100644
--- a/next.config.js
+++ b/next.config.js
@@ -17,6 +17,8 @@ const config = {
locales: ["en"],
defaultLocale: "en",
},
+
+ transpilePackages: ["next-auth"],
};
export default config; From nextauthjs/next-auth#9385 (comment). This appears to work as expected with:
|
Provide environment information
Happening in the latest version available: create-t3-app@7.38.1.
Describe the bug
On public and protected routes, the tRPC calls made from the client fail indicating the following error:

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.

The text was updated successfully, but these errors were encountered: