Build fails on Next.js 15.4.5 with TypeError: Cannot read properties of null (reading 'useContext') during prerendering of /404

[jsdev-robin]

Link to the code that reproduces this issue

https://github.com/vercel/turborepo/tree/main/examples/with-tailwind

To Reproduce

1. Use Next.js 15.4.5
2. Run npm install
3. Run next build
4. You will see:

TypeError: Cannot read properties of null (reading 'useContext') at p (...\.next\server\pages\_error.js:19:2590) Error occurred prerendering page "/404". Read more: https://nextjs.org/docs/messages/prerender-error Export encountered an error on /_error: /404, exiting the build. ⨯ Next.js build worker exited with code: 1 and signal: null

Current vs. Expected behavior

next build should complete successfully and statically export all pages including /404 and /_error.

Actual:
Build fails with a runtime error during prerendering.

Provide environment information

Operating System: Windows 11 64-bit
Node.js Version: 20.12.2
npm Version: 10.5.0
Package Manager: npm
Next.js Version: 15.4.5
Hosting: Local

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

Turbopack

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

next build (local)

Additional context

Suspected root cause: useContext called on null during _error.js or /404 rendering in static export

auto-install-peers warning likely unrelated, but present

I tested disabling the _error.tsx file, and build succeeds

Disabling "output": "standalone" does not fix the issue

_NEXT-4720

[eps1lon]

I can't repro with

$ npx create-turbo@latest -e with-tailwind
$ npm install
$ npm run build

on the same Node.js version and Microsoft Windows 11 Pro N 10.0.26100 N/A Build 26100

@jsdev-robin Were these the exact steps you tried to reproduce with?

The example doesn't use Turbopack builds and I had no issues building with Turbopack so I'm removing the Turbopack label.

[jsdev-robin]

I can't repro with

$ npx create-turbo@latest -e with-tailwind
$ npm install
$ npm run build

@jsdev-robin Were these the exact steps you tried to reproduce with?

The example doesn't use Turbopack builds and I had no issues building with Turbopack so I'm removing the Turbopack label.

Yes, I followed exactly these steps:

npx create-turbo@latest -e with-tailwind
npm install
npm run build

However, I encountered the issue when building with Turbopack. It seems that while the example itself may not use Turbopack, in my local setup Turbopack was enabled, which could be causing the difference in results.

[jsdev-robin]

[eps1lon]

I also tried with Turbopack and it did work. Please include a repro with the code you have locally. It's not clear where you added the --turbopack flag. Could also be an issue with your lockfile which is why a cloneable repro of your code is so important.

[jsdev-robin]

I also tried with Turbopack and it did work. Please include a repro with the code you have locally. It's not clear where you added the --turbopack flag. Could also be an issue with your lockfile which is why a cloneable repro of your code is so important.

This issue occurs with npm, but not with pnpm. In the project, the default two apps web and docs build successfully with npm. However, when a new app is installed, this issue appears. After installing a new app using npx create-next-app@latest apps/new-app, running the build command results in an error.

[icyJoseph]

Mmm I was able to get some similar error message, all I did was cd into apps, and create-next-app a new project. Then back up to the root, and npm run build errored - I ran npm dedupe at the root and it worked again 🤔 -

I think the problem is that the create-next-app has a pinned dep to 19.1.0 react and react-dom - cuz installing 19.1.1 kind works too, but I am guessing at this point. Please do make a repository - including lock file - with a broken state.

[jsdev-robin]

Mmm I was able to get some similar error message, all I did was cd into apps, and create-next-app a new project. Then back up to the root, and npm run build errored - I ran npm dedupe at the root and it worked again 🤔 -

I think the problem is that the create-next-app has a pinned dep to 19.1.0 react and react-dom - cuz installing 19.1.1 kind works too, but I am guessing at this point. Please do make a repository - including lock file - with a broken state.

Bro, I’ve already fixed it. Thanks a lot for your feedback!

[ukcw]

hey, how did you fix this?

[jsdev-robin]

hey, how did you fix this?

I used pnpm instead of npm because it is recommended for monorepos and maintains the lockfile more efficiently.

[andrewpeters9]

FYI, upgrading to 15.5.1-canary.4 fixed this issue for me

[Vercjames]

Error persists. Next 15.5.3. Fresh npmx create-next-app.

npx create-next-app@latest
✔ What is your project named? … my-test
✔ Would you like to use TypeScript? … No / Yes
✔ Which linter would you like to use? › ESLint
✔ 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? (recommended) … No / Yes
✔ Would you like to customize the import alias (@/* by default)? … No / Yes

[TypeError: Cannot read properties of null (reading 'useContext')]
Error occurred prerendering page "/404". Read more: https://nextjs.org/docs/messages/prerender-error
[TypeError: Cannot read properties of null (reading 'useContext')]
Export encountered an error on /_error: /404, exiting the build.
⨯ Next.js build worker exited with code: 1 and signal: null

[icyJoseph]

Unfortunately this doesn't happen to everybody, it is actually not really clear what's happening...

@Vercjames which React and React-DOM versions do yo have?