Build error with Next.js 15 in monorepo

[omarshehab221]

Link to the code that reproduces this issue

https://github.com/omarshehab221/DoomUI

To Reproduce

Just clone the repo and try to build the apps/template or the apps/playground (I made sure not change anything in this one from what bun create next-app@latest created to test the error)

Current vs. Expected behavior

I was trying to build the apps/template without that much change from what bun create next-app@latest created. I expected it to build fine specially that it passed the optimized build and the linting phases. It throws this error in the Collecting pages data phase: "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."

I created apps/playground and made sure not to change any of its code just to be sure the issue exists and had the same problem.

This usually doesn't happen when I'm not working in a monorepo

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 16272
  Available CPU cores: 4
Binaries:
  Node: 18.18.0
  npm: 10.5.0
  Yarn: 1.22.22
  pnpm: 9.9.0
  bun: 1.1.33
Relevant Packages:
  next: 15.0.3
  eslint-config-next: 15.0.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

create-next-app, Output (export/standalone), Turbopack

Which stage(s) are affected? (Select all that apply)

next build (local)

Additional context

I created apps/playground and didn't change it's code just to test this

[body20002]

A workaround for this issue is to not use turbopack,
this bug was open in turborepo/#6298 before moving turbopack to vercel/nextjs repo.

[gameriff]

A workaround for this issue is to not use turbopack, this bug was open in turborepo/#6298 before moving turbopack to vercel/nextjs repo.

The issue you reference seems to be in regard to using turbopack for dev, but this issue (which I am also experiencing) is referring to running a full build in a monorepo, if I am not mistaken.

[body20002]

@gameriff yeah sorry I didn't try to build before commenting and I was facing issues with a monorepo setup with nextjs 15, building seems to be fine on my end but again I'm not using turborepo just bun workspaces.

[Thaigun]

I can confirm the same issue, trying to build a project created by create-next-app. I tried with both Bun and Node and did not select Turbopack when setting up. I'm also in a workspaces monorepo.

[gameriff]

I was able to get my workspaces monorepo (note: I manually created this monorepo, i.e., not using create-react-app or other init script) to build with Next 15.0.3 and react/react-dom 19 release candidate versions by:

• Ensuring that my root package.json has the recommended types-react overrides set, as detailed here React 19 RC Upgrade Guide:

{ "dependencies": { "@types/react": "npm:types-react@rc", "@types/react-dom": "npm:types-react-dom@rc" }, "overrides": { "@types/react": "npm:types-react@rc", "@types/react-dom": "npm:types-react-dom@rc" } }

and by removing any @types/react dependencies in any of the workspace package.jsons.

And then:

• Installing the same react 19 release candidate version (whichever you choose, check NPM for latest) in all workspace packages, which, in my case, with my other dependencies, required using the --force --legacy-peer-deps flags to get a successful installation.

• I did end up deleting .next/cache, my package-lock.json and all of my node_modules directories at some point as well, as I was experimenting, but hard to tell if this was necessary or not.

[markomitranic]

This issue made me go insane until i carefully read the comment #72899 (comment) from @gameriff .

I was already doing all those things, but it didn't work. The trick was to use BOTH --force and --legacy-peer-deps flags. Thank you <3

I hate this.