Fresh next install build fails - next 15.2.2
Unanswered
JeffBaumgardt posted this in #help-forum
Very simple start. Create a new app via the cli
I ran a
The only outside thing that I can think of is this project is inside a turborepo monorepo with other apps that are on different versions of next, react and react-dom. I wouldn't expect these things to cross streams but I don't really know. The attached cli output does not have a good stack trace.
It looks like it's complaining about /500 or /404 but this is a fresh init, there are no such files/routes in a fresh setup, next just uses the internal ones.
npx create-next-app@latest customer-service-portal and then cd to customer-service-portal.I ran a
npm i just incase. I ran npm run build very next. I expect this to just run without issue. There are 0 code changes.The only outside thing that I can think of is this project is inside a turborepo monorepo with other apps that are on different versions of next, react and react-dom. I wouldn't expect these things to cross streams but I don't really know. The attached cli output does not have a good stack trace.
It looks like it's complaining about /500 or /404 but this is a fresh init, there are no such files/routes in a fresh setup, next just uses the internal ones.
45 Replies
➜ customer-service-portal git:(bootstrap-customer-service-portal) npm run build
> customer-service-portal@0.1.0 build
> next build
▲ Next.js 15.2.2
Creating an optimized production build ...
✓ Compiled successfully
✓ Linting and checking validity of types
✓ Collecting page data
[Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7B%24%24typeof%2C%20type%2C%20key%2C%20ref%2C%20props%7D for the full message or use the non-minified dev environment for full errors and additional helpful warnings.]
Error occurred prerendering page "/500". Read more: https://nextjs.org/docs/messages/prerender-error
Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7B%24%24typeof%2C%20type%2C%20key%2C%20ref%2C%20props%7D for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at Z (/Users/jeff/Projects/user-frontend/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:490)
at Xc (/Users/jeff/Projects/user-frontend/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:409)
at Zc (/Users/jeff/Projects/user-frontend/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:210)
at Z (/Users/jeff/Projects/user-frontend/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
at Zc (/Users/jeff/Projects/user-frontend/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
at Z (/Users/jeff/Projects/user-frontend/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
at $c (/Users/jeff/Projects/user-frontend/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
at bd (/Users/jeff/Projects/user-frontend/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:77:404)
at Z (/Users/jeff/Projects/user-frontend/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:217)
at Zc (/Users/jeff/Projects/user-frontend/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:479)
Export encountered an error on /_error: /500, exiting the build.
⨯ Next.js build worker exited with code: 1 and signal: null
npm error Lifecycle script `build` failed with error:
npm error code 1
npm error path /Users/jeff/Projects/user-frontend/apps/customer-service-portal
npm error workspace customer-service-portal@0.1.0
npm error location /Users/jeff/Projects/user-frontend/apps/customer-service-portal
npm error command failed
npm error command sh -c next buildnpm run dev works just fine no errors.Yeah dev was no problem
I also ran builds on other apps in the mono and they are fine.
Dutch
rm -rf .next && npm run buildSame export error
It switches between /500 and /404 as the reported path. Which is random.
It switches between /500 and /404 as the reported path. Which is random.
I did find this article that kind of verifies the issue
https://github.com/vercel/turborepo/issues/9335
Might be conflicting react's. Not sure why. I'm just changing the deps now and try another build. brb
https://github.com/vercel/turborepo/issues/9335
Might be conflicting react's. Not sure why. I'm just changing the deps now and try another build. brb
Dutch
yea use next@14.x
It's all very strange because my other apps in the mono also use next 15 just different minor 15.1.
Dutch
staying at old versions until next version comes worked for me all the time
I have one that's also running at 15.2.2. So that's not it there.
Dutch
can i see it live in vscode live share
Umm. Interesting. I'm on cursor and I havn't tried live share in a few years. Let me check.
Dutch
or will i run that command and see
I imaging it should just work. But you might have to do a turbopack mono first.
Dutch
> customer-service-portal@0.1.0 build
> next build
▲ Next.js 15.2.2
Creating an optimized production build ...
✓ Compiled successfully
✓ Linting and checking validity of types
✓ Collecting page data
✓ Generating static pages (5/5)
✓ Collecting build traces
✓ Finalizing page optimization
Route (app) Size First Load JS
┌ ○ / 5.57 kB 106 kB
└ ○ /_not-found 977 B 102 kB
+ First Load JS shared by all 101 kB
├ chunks/4bd1b696-5b6c0ccbd3c0c9ab.js 53.2 kB
├ chunks/684-dff6e8585da7670f.js 45.3 kB
└ other shared chunks (total) 1.96 kB
○ (Static) prerendered as static content√ Would you like to use TypeScript? ... No / Yes
√ Would you like to use ESLint? ... No / Yes
√ Would you like to use Tailwind CSS? ... No / Yes
√ Would you like your code inside a `src/` directory? ... No / Yes
√ Would you like to use App Router? (recommended) ... No / Yes
√ Would you like to use Turbopack for `next dev`? ... No / __Yes__
√ Would you like to customize the import alias (`@/*` by default)? ... No / Yes
√ What import alias would you like configured? ... @/*Yeah I'm pretty sure that it has to be something with conflicting deps between the workspaces. Seems like a shame. But that's what you get when you use mono's I guess.
Dutch
what is mono
Monorepo
Dutch
i just ran that command you shared
I am using turborepo (also by vercel) for keeping multiple apps and packages in one repo.
Dutch
then your turborepo setup having problems not normal fresh installs right
Yes.
In a sence
Dutch
then we need live share 😄
if cursor can connect to vscode via that link idk
If I do a absolute new project not inside my mono then create-next-app works.
Yeah it's the root package-lock.json with conflicting react / react-dom 18 and 19 versions. Looks like all my apps need to be on one version or the other. Even between descret apps in the workspace.
Dutch
so its solved
I mean by yes not mixing the versions of react between projects.
Not ideal, as react is not a dependency on the mono, but at least it's something I have to make a specific note of for others.
Dutch
you can describe it in root package.json file
probably peerDependencies
I can. But the root should not have dependencies on react. Maybe peer. But this issue is much deeper than that.
This is a truborepo issue and not a nextjs. But turborepo closed their discord in favor of moving here.
Dutch
at least its not what you wrote at title 😄
open an issue on turborepo maybe
or use nx
🤦 This is the place they told turborepo to go.
I think I'll wait for one of the mods that can chime in.
I do not want to use nx as turborepo up until this point has been great.
Dutch
there is discussions channel also
@Moderator