next.js: [NEXT-1231] This is probably a bug in the React Server Components bundler.

Verify canary release

I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.16.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.4.3
      eslint-config-next: 13.4.3
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4

warn  - Latest canary version not detected, detected: "13.4.3", newest: "13.4.4-canary.6".
        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) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

npx create-next-app --example reproduction-template-app-dir reproduction-app

To Reproduce

When attempting to generate a new Next.js project using the command npx create-next-app@latest, I encountered an error in app-router.js# related to the React Client Manifest. This error is likely due to a bug in the React Server Components bundler, which was triggered after running the npm run dev command.

Describe the Bug

Expected Behavior

Generate a new Next.js app with the latest features

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

_NEXT-1231

About this issue

Original URL
State: closed
Created a year ago
Comments: 36 (7 by maintainers)

Commits related to this issue

Fix tracking of ContextModule (#52795) When doing dynamic imports like `import(variable)`, Webpack _tries_ to statically analyze it and creates a regex like context module for it (which includes all ... — committed to vercel/next.js by shuding a year ago

Most upvoted comments

Getting the following error:

Error: Could not find the module "/Users/[user]/Projects/ProjectName/components/Modal.tsx#" in the React Client Manifest. This is probably a bug in the React Server Components bundler.

NextJs version: "next": "^13.4.10",

Node version: v18.16.0

I’m using the Intercepting Routes feature.

It was working yesterday, I updated NextJs today, and it is not working anymore.

app
- layout.tsx (modal is added in the layout)
- page.tsx
- project/[id]
  - page.tsx
- @modal
  - (.)project/[id]
    - page.tsx

Things I’ve tried so far without success:

Delete .next folder
Delete node_modules folder
Delete package-lock.json
npm cache clean --force
npm install

+11

keno-reloaded on Jul 15, 2023

@dihan48 Are you going to create the new issue, or should I?

khuezy on Jul 19, 2023

Same issue when upgrading from 13.4.9 to 13.4.10.

arobert93 on Jul 17, 2023

Getting the following error:

Error: Could not find the module "/Users/[user]/Projects/ProjectName/components/Modal.tsx#" in the React Client Manifest. This is probably a bug in the React Server Components bundler.

NextJs version: "next": "^13.4.10",

Node version: v18.16.0

I’m using the Intercepting Routes feature.

It was working yesterday, I updated NextJs today, and it is not working anymore.

app

layout.tsx (modal is added in the layout)

page.tsx

project/[id]

page.tsx

@modal

(.)project/[id]

page.tsx

Things I’ve tried so far without success:

Delete .next folder

Delete node_modules folder

Delete package-lock.json

npm cache clean --force

npm install

I was facing the same issue, downgrading to 13.4.7 fixed the problem. The nextgram example is using that version.

piedrahitapablo on Jul 16, 2023

@gokulkrishh I had the same error. In my case I was implementing global-error.tsx and I was getting this issue during the productive build, I removed it and it’s working properly now

ctkc on Jul 12, 2023

@stevedeighton I am having similar issue but for different file. Still trying to figure out what it it.

Error: Could not find the module "/vercel/path0/node_modules/next/dist/client/components/error-boundary.js#" in the React Client Manifest. This is probably a bug in the React Server Components bundler.
    at gb (/var/task/.next/server/chunks/2578.js:7033:27)
    at Ya (/var/task/.next/server/chunks/2578.js:7107:38)
    at Object.toJSON (/var/task/.next/server/chunks/2578.js:6871:20)
    at stringify (<anonymous>)
    at ib (/var/task/.next/server/chunks/2578.js:7278:9)
    at fb (/var/task/.next/server/chunks/2578.js:7177:29)
    at Timeout._onTimeout (/var/task/.next/server/chunks/2578.js:7002:16)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '1623416432'
}

gokulkrishh on Jul 12, 2023

I think this is about as small a repro as I can make it. The issue seems to stem from using a dynamic import. I’ve personally encountered this while loading MDX components, but this can occur with any kind of component.

Repro: https://github.com/alexkirsz/next-app-router-dynamic-issue

alexkirsz on Jul 10, 2023