nextjs - 💡(How to fix) Fix TypeError: Cannot read properties of undefined (reading 'createClientModuleProxy') [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#84841Fetched 2026-04-08 02:18:12
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×2closed ×1commented ×1issue_type_added ×1

Error Message

⨯ TypeError: Cannot read properties of undefined (reading 'createClientModuleProxy') at webpack_require (.next/server/webpack-runtime.js:33:42) at webpack_require (.next/server/webpack-runtime.js:33:42) at webpack_require (.next/server/webpack-runtime.js:33:42) at webpack_exec (.next/server/app/_not-found/page.js:234:39) at <unknown> (.next/server/app/_not-found/page.js:235:1882) at webpack_require.X (.next/server/webpack-runtime.js:163:21) at <unknown> (.next/server/app/_not-found/page.js:235:47) at Object.<anonymous> (.next/server/app/_not-found/page.js:238:3)

Code Example

TypeError: Cannot read properties of undefined (reading 'createClientModuleProxy')
    at __webpack_require__ (.next/server/webpack-runtime.js:33:42)
    at __webpack_require__ (.next/server/webpack-runtime.js:33:42)
    at __webpack_require__ (.next/server/webpack-runtime.js:33:42)
    at __webpack_exec__ (.next/server/app/_not-found/page.js:234:39)
    at <unknown> (.next/server/app/_not-found/page.js:235:1882)
    at __webpack_require__.X (.next/server/webpack-runtime.js:163:21)
    at <unknown> (.next/server/app/_not-found/page.js:235:47)
    at Object.<anonymous> (.next/server/app/_not-found/page.js:238:3)

---

Operating System:
  Platform: linux
  Arch: x64
  Version: #85-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 18 15:26:59 UTC 2025
  Available memory (MB): 64192
  Available CPU cores: 16
Binaries:
  Node: 24.4.0
  npm: 11.4.2
  Yarn: N/A
  pnpm: 10.13.1
Relevant Packages:
  next: 15.2.5 // There is a newer version (15.5.5) available, upgrade recommended! 
  eslint-config-next: 15.5.4
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.9.3
Next.js Config:
  output: N/A
There is a newer version (15.5.5) available, upgrade recommended! 
   Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
   Read more - https://nextjs.org/docs/messages/opening-an-issue
RAW_BUFFERClick to expand / collapse

To Reproduce

node node_modules/next/dist/bin/next dev works nx run ui-main:serve not

⨯ TypeError: Cannot read properties of undefined (reading 'createClientModuleProxy')
    at __webpack_require__ (.next/server/webpack-runtime.js:33:42)
    at __webpack_require__ (.next/server/webpack-runtime.js:33:42)
    at __webpack_require__ (.next/server/webpack-runtime.js:33:42)
    at __webpack_exec__ (.next/server/app/_not-found/page.js:234:39)
    at <unknown> (.next/server/app/_not-found/page.js:235:1882)
    at __webpack_require__.X (.next/server/webpack-runtime.js:163:21)
    at <unknown> (.next/server/app/_not-found/page.js:235:47)
    at Object.<anonymous> (.next/server/app/_not-found/page.js:238:3)

Current vs. Expected behavior

node node_modules/next/dist/bin/next dev should work

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #85-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 18 15:26:59 UTC 2025
  Available memory (MB): 64192
  Available CPU cores: 16
Binaries:
  Node: 24.4.0
  npm: 11.4.2
  Yarn: N/A
  pnpm: 10.13.1
Relevant Packages:
  next: 15.2.5 // There is a newer version (15.5.5) available, upgrade recommended! 
  eslint-config-next: 15.5.4
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.9.3
Next.js Config:
  output: N/A
 ⚠ There is a newer version (15.5.5) available, upgrade recommended! 
   Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
   Read more - https://nextjs.org/docs/messages/opening-an-issue

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

Webpack

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

next dev (local)

Additional context

No response

extent analysis

TL;DR

Upgrade to the latest version of Next.js (15.5.5) to potentially resolve the TypeError: Cannot read properties of undefined (reading 'createClientModuleProxy') issue.

Guidance

  • The error message suggests a compatibility issue with the current version of Next.js (15.2.5) and Webpack.
  • Upgrading to the latest version of Next.js (15.5.5) may resolve the issue, as recommended in the environment information section.
  • Before upgrading, try installing the latest canary version (npm install next@canary) to confirm the issue still exists.
  • Verify the issue by running nx run ui-main:serve after upgrading to the latest version.

Notes

  • The issue may be specific to the combination of Next.js, Webpack, and the nx run ui-main:serve command.
  • Upgrading to the latest version of Next.js may introduce other compatibility issues, so thorough testing is recommended.

Recommendation

  • Upgrade to the latest version of Next.js (15.5.5), as it may resolve the issue and provide other bug fixes and improvements.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix TypeError: Cannot read properties of undefined (reading 'createClientModuleProxy') [1 comments, 2 participants]