-
Notifications
You must be signed in to change notification settings - Fork 4k
Open
Labels
bugSomething isn't workingSomething isn't workingtriageUnseen or unconfirmed by a maintainer yet. Provide extra information in the meantime.Unseen or unconfirmed by a maintainer yet. Provide extra information in the meantime.
Description
Environment
System:
OS: Linux 6.8 Ubuntu 24.04.3 LTS 24.04.3 LTS (Noble Numbat)
CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
Memory: 21.08 GB / 31.06 GB
Container: Yes
Shell: 5.2.21 - /bin/bash
Binaries:
Node: 22.17.0 - /run/user/1000/fnm_multishells/117412_1767514956193/bin/node
npm: 10.9.2 - /run/user/1000/fnm_multishells/117412_1767514956193/bin/npm
Browsers:
Chrome: 143.0.7499.169
Firefox: 146.0.1
Firefox Developer Edition: 146.0.1
npmPackages:
next: 15.5.9 => 15.5.9
next-auth: ^5.0.0-beta.30 => 5.0.0-beta.30
react: 19.2.3 => 19.2.3
Reproduction URL
https://test-next-auth-theta.vercel.app/
Describe the issue
After building an app using next-auth@beta + NextJS v15 + Turbopack, the console shows an error when the custom login page is shown. It uses a custom login page
If you use it using npm run dev everything works very well. But if you run npm run build and npm run start the browser console shows an error like the attached image
I believe it's a problem when building with turbopack because it's working when you're not using it.
Repository is available here
How to reproduce
- Build the app:
npm run build - Serve it
npm run start - Go to:
localhost:3000, the app will redirect you to/signin - The page is not rendered properly and it shows errors on the browser console
Expected behavior
The login page should be shown properly and we should be able to log in
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingtriageUnseen or unconfirmed by a maintainer yet. Provide extra information in the meantime.Unseen or unconfirmed by a maintainer yet. Provide extra information in the meantime.
