nextjs - 💡(How to fix) Fix Next.js 16.0.3: Build fails with React hooks errors on auto-generated pages (React 19.2) [1 comments, 2 participants]

Description

Next.js 16.0.3 production build fails with TypeError: Cannot read properties of null (reading 'useState') when generating auto-generated pages (/_not-found, /_global-error). This is a regression from 16.0.0 which builds successfully with the same code.

Environment

• Next.js: 16.0.3
• React: 19.2.0
• React DOM: 19.2.0
• Node.js: 22.16.0
• OS: Windows 11
• Package Manager: Yarn 1.22.22
• Build Tool: Turbopack (default in 16.0.3)

Relevant package.json:

{
  "dependencies": {
    "next": "^16.0.3",
    "react": "^19.2.0",
    "react-dom": "^19.2.0"
  },
  "devDependencies": {
    "eslint-config-next": "^16.0.3",
    "typescript": "^5.9.2"
  }
}

next.config.js:

export default {
  turbopack: {},
  reactCompiler: true,
  experimental: {
    turbopackFileSystemCacheForDev: true,
  },
  serverExternalPackages: ['@duckdb/node-api', 'msnodesqlv8', 'mssql']
};

Steps to Reproduce

1. Start with a working Next.js 16.0.0 project (React 19.2.0)
2. Update package.json:
   • next: ^16.0.0 → ^16.0.3
   • eslint-config-next: ^16.0.0 → ^16.0.3
3. Clean install:

   rm -rf node_modules .next yarn.lock
   yarn install

4. Run production build:

   yarn build

Expected Behavior

Production build completes successfully, as it does on Next.js 16.0.0.

Actual Behavior

Build fails during static page generation on /_not-found:

Error occurred prerendering page "/_not-found". Read more: https://nextjs.org/docs/messages/prerender-error
TypeError: Cannot read properties of null (reading 'useState')
    at e (.next\server\chunks\ssr\[root-of-the-server]__0238eb7a._.js:1:6782) {
  digest: '569475980'
}
Export encountered an error on /_not-found/page: /_not-found, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

Additional Error Variant: If NODE_ENV=development is manually set in .env (which violates Next.js best practices), the error occurs on /_global-error instead:

TypeError: Cannot read properties of null (reading 'useContext')
    at ignore-listed frames {
  digest: '2522360787'
}

Turbopack Dev Server Also Fails

Running yarn dev with Turbopack crashes immediately:

FATAL: An unexpected Turbopack error occurred
Turbopack Error: Failed to write app endpoint /page

A panic log has been written to %TEMP%\next-panic-*.log

What We've Verified

✅ Clean dependency reinstall - Removed node_modules, .next, yarn.lock, reinstalled from scratch
✅ No NODE_ENV in .env - Removed manual NODE_ENV setting per Next.js docs
✅ No React version conflicts - yarn list react shows single React 19.2.0 instance
✅ Not a monorepo - Simple Next.js App Router project, no nested dependencies
✅ TypeScript passes - tsc --noEmit completes without errors
✅ No custom error pages - No custom global-error.tsx or not-found.tsx files
✅ Fresh .next cache - Multiple clean builds attempted

Workaround

Downgrade to Next.js 16.0.0 - Production build and dev server work perfectly with identical code.

# In package.json
"next": "^16.0.0"
"eslint-config-next": "^16.0.0"

Additional Context

• The errors only occur on auto-generated Next.js pages (/_not-found, /_global-error)
• All application routes, pages, and APIs work correctly in development on 16.0.0
• Issue appears specific to React 19.2 + Next.js 16.0.3 combination
• Related closed issue: #85668 (resolution was dependency cleanup, which we've done thoroughly)
• No middleware or special routing configurations

Possibly Related Commits

This regression likely occurred in commits between 16.0.0 and 16.0.3 affecting:

• React hooks handling in SSR/static generation
• Auto-generated error page rendering
• Turbopack page bundling

System Information

Operating System:
  Platform: win32
  Version: Windows 11

Binaries:
  Node: 22.16.0
  npm: N/A
  Yarn: 1.22.22

Relevant Packages:
  next: 16.0.3
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.9.2

Next.js Config:
  output: N/A
  turbopack: enabled (default)