[NEXT-1231] This is probably a bug in the React Server Components bundler. #50243

codeawy · 2023-05-24T02:12:38Z

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

The text was updated successfully, but these errors were encountered:

hiramhuang · 2023-05-25T09:33:25Z

Same issue here. I'm running on next@13.4.2, and this error only occur on production build.

codeawy · 2023-05-25T10:29:09Z

I tried to generate a new project now, and this working fine ❤️

leimonio · 2023-06-09T15:08:34Z

I'm facing a similar issue running NextJS application through a custom http server, using the next module v13.4.4
The module itself exists in the given path, but there is also a hash appended.

Uncaught Error: Could not find the module "{absolutePathToFolder}/bit-next-app-type/node_modules/.pnpm/next@13.4.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/client/image.js#" in the React Client Manifest. This is probably a bug in the React Server Components bundler.
    at resolveClientReferenceMetadata (webpack-internal:///(sc_server)/../../../../../.pnpm/next@13.4.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-server.edge.development.js:205:27)

leimonio · 2023-06-09T16:29:29Z

@shuding After a bit further debugging of this it seems like webpackMap here only includes references from inside components folder but nothing related to the client/image.js. Is this an expected behavior?

https://github.com/vercel/next.js/blob/2226d2935f04e10de0a5d563067e7d32e6872f00/packages/next/src/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-server.edge.development.js#LL2948C10-L2948C32

Abhishek-Selfridges · 2023-06-12T16:58:04Z

I am still getting the same error when trying to execute npm run dev . I am trying to create a new next js project using npx create-next-app . I tried with both the @latest and without latest and for both it gives same error in sonsole as **Could not find the module app-router.js in the React Client Manifest. This is probably a bug in the React Server Components bundler. **

@shuding @codeawy

leimonio · 2023-06-13T08:21:36Z

@Abhishek-Selfridges can you please raise a new issue? my setup is a bit more complicated to share at the moment, so I think the team would really appreciate it if they have more detailed information about how to reproduce this issue.

simrin3308 · 2023-06-23T05:30:36Z

Faced the same error today. Any fix?

shawnesquivel · 2023-06-30T23:54:35Z

Any fix for this? Finding that some people can run npm install on my project, but when they run npm run dev they get this error.

desca96aws · 2023-07-01T02:08:46Z

I get the same issue in the browser, this is what I get in the terminal

gharis94 · 2023-07-03T04:52:29Z

I am having the same issue, did anyone resolve it? if yes then please share.

darasus · 2023-07-03T11:11:58Z

I'm getting similar issue only when running route on edge.

Error: Could not find the module "/vercel/path0/apps/web/src/components/Marketing/GetStartedButton.tsx#GetStartedButton" in the React Client Manifest. This is probably a bug in the React Server Components bundler.
    at (../../node_modules/.pnpm/next@13.4.8-canary.14_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/react-server-dom-webpack-experimental/cjs/react-server-dom-webpack-server.edge.production.min.js:35:327)
    at (../../node_modules/.pnpm/next@13.4.8-canary.14_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/react-server-dom-webpack-experimental/cjs/react-server-dom-webpack-server.edge.production.min.js:40:79)
    at (../../node_modules/.pnpm/next@13.4.8-canary.14_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/react-server-dom-webpack-experimental/cjs/react-server-dom-webpack-server.edge.production.min.js:29:150)
    at (../../node_modules/.pnpm/next@13.4.8-canary.14_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/react-server-dom-webpack-experimental/cjs/react-server-dom-webpack-server.edge.production.min.js:50:197)
    at (../../node_modules/.pnpm/next@13.4.8-canary.14_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/react-server-dom-webpack-experimental/cjs/react-server-dom-webpack-server.edge.production.min.js:45:449)
    at (../../node_modules/.pnpm/next@13.4.8-canary.14_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/react-server-dom-webpack-experimental/cjs/react-server-dom-webpack-server.edge.production.min.js:33:406)

stevedeighton · 2023-07-03T20:28:29Z

I'm seeing this error when using the Image component. I'm on next@13.4.8 which was released just a few hours ago. Everything is working as expected until I use the Image component. I get this error...

Error: Could not find the module "MY_PROJECT_PATH/node_modules/next/dist/client/image-component.js#Image" in the React Client Manifest. This is probably a bug in the React Server Components bundler.

I also see this in the terminal...

error node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-server.edge.development.js (188:12) @ resolveClientReferenceMetadata.

Maybe this issue can be reopened please?

eliasbauer1 · 2023-07-08T20:33:26Z

Solved the problem

Solve: I added "use client" in the parent component.
Explanation: I rendered the child component dynamically, so if I tried to use useEffect on the child component, it didn't work. For it to not get rendered on the server (and throw the error) I added "use client".

alexkirsz · 2023-07-10T10:33:07Z

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

stevedeighton · 2023-07-10T10:51:37Z

alexkirsz/next-app-router-dynamic-issue

Yes good call. My project is using dynamic imports too!

stevedeighton · 2023-07-10T13:41:45Z

@alexkirsz Looks like this issue isn't isolated to the Image component, as I'm getting the same error when using the link component in a component that's dynamically imported.

Error: Could not find the module "/MY_PROJECT_PATH/node_modules/next/dist/client/link.js#" in the React Client Manifest. This is probably a bug in the React Server Components bundler.

gokulkrishh · 2023-07-12T10:14:02Z

@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 · 2023-07-12T11:33:51Z

Found out that error.tsx file for error handling was missing. Even though there was no error in development but got the above issue in production.

ctkc · 2023-07-12T14:24:21Z

@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

gokulkrishh · 2023-07-12T15:16:36Z

@ctkc Yes looks like it, global-error.tsx file caused this issue. Resolved it by removing it. Thanks.

stevedeighton · 2023-07-12T15:20:15Z

I have also spotted this error using useState. It appears anything that's client side isn't working with dynamic imports, unless I'm doing something totally wrong. I have tried adding use client to all of my components but it's still not playing nice. I'll be reverting to the pages router for now :(

louisthomaspro · 2023-07-15T05:14:06Z

This error is so weird.. I had it for a moment. I switched branch, then came back to the my main branch. And the error disappeared.
My error log was:

Error: Could not find the module "/home/git/project/components/side-sheet-wrapper.tsx#SideSheetWrapper" in the React Client Manifest. This is probably a bug in the React Server Components bundler.

keno-reloaded · 2023-07-15T09:00:18Z

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

askinbilir · 2023-07-15T18:52:48Z

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 faced with same issue, I don't know the problem, but I guess client components cause the crash when I remove them it's working so if you convert all components to server components, probably will work.

IamSolaSholzy01 · 2023-07-16T00:40:29Z

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'm now facing the same issue after upgrading from Next 13.4.7 to 13.4.10.
V13.4.8 had a different issue, that caused a client exception.

monzim · 2023-07-16T11:40:08Z

Same issue
NextJs version: "next": "13.4.10",
React: "react": "18.2.0",

`@modal

(.)project/[id]

page.tsx`

piedrahitapablo · 2023-07-16T23:30:39Z

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.

acomanescu · 2023-07-17T08:13:48Z

Same issue when upgrading from 13.4.9 to 13.4.10.

piedrahitapablo · 2023-07-17T14:45:40Z

I think this is related to #52681

@alexkirsz

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 possible modules). This `ContextModule` doesn't have a resource path so we need to use the identifier to track it. Tested with @alexkirsz's repro here #50243 (comment) and confirmed that it fixes the problem. Closes #50243.

pawanrana1992 · 2023-07-18T04:27:58Z

Guys please remove global-error.tsx it is the culprit here. I tried many things but this issue with error handling from nextjs side. Nextjs team should look into it on priority.
version: "next": "13.4.10", (app-directory)

timneutkens · 2023-07-18T08:45:46Z

@pawanrana1992 can you share a reproduction of your application where it fails in a new issue? Might be something in the file? I.e. maybe not rendering <html> etc.?

dihan48 · 2023-07-18T09:52:50Z

@timneutkens https://stackblitz.com/github/easydevgit/next-13-course/tree/master/advanced-routing-intercepting-routes

timneutkens · 2023-07-18T12:47:41Z

Please open a new issue as I requested.

julioflima · 2023-07-18T20:45:13Z

@timneutkens https://stackblitz.com/github/easydevgit/next-13-course/tree/master/advanced-routing-intercepting-routes

Tested using 13.4.11-canary.0.

Same!

khuezy · 2023-07-19T01:20:52Z

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

timneutkens · 2023-07-19T09:52:49Z

I'm going to lock this issue, please read my earlier comments.

codeawy added the bug Issue was opened via the bug report template. label May 24, 2023

shuding added the linear: next Confirmed issue that is tracked by the Next.js team. label May 24, 2023

shuding changed the title ~~This is probably a bug in the React Server Components bundler.~~ [NEXT-1231] This is probably a bug in the React Server Components bundler. May 24, 2023

codeawy closed this as completed May 25, 2023

alexkirsz reopened this Jul 8, 2023

shuding self-assigned this Jul 17, 2023

shuding mentioned this issue Jul 17, 2023

Fix tracking of ContextModule #52795

Merged

kodiakhq bot closed this as completed in #52795 Jul 17, 2023

khuezy mentioned this issue Jul 17, 2023

Fix: react resolution for interception, parallel and group routes opennextjs/opennextjs-aws#155

Closed

vercel locked and limited conversation to collaborators Jul 19, 2023

[NEXT-1231] This is probably a bug in the React Server Components bundler. #50243

[NEXT-1231] This is probably a bug in the React Server Components bundler. #50243

Comments

codeawy commented May 24, 2023 • edited by shuding Loading

Verify canary release

Provide environment information

Which area(s) of Next.js are affected? (leave empty if unsure)

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

To Reproduce

Describe the Bug

Expected Behavior

Which browser are you using? (if relevant)

How are you deploying your application? (if relevant)

hiramhuang commented May 25, 2023

codeawy commented May 25, 2023

leimonio commented Jun 9, 2023 • edited Loading

leimonio commented Jun 9, 2023 • edited Loading

Abhishek-Selfridges commented Jun 12, 2023

leimonio commented Jun 13, 2023

simrin3308 commented Jun 23, 2023

shawnesquivel commented Jun 30, 2023

desca96aws commented Jul 1, 2023

gharis94 commented Jul 3, 2023

darasus commented Jul 3, 2023 • edited Loading

stevedeighton commented Jul 3, 2023 • edited Loading

eliasbauer1 commented Jul 8, 2023

Solved the problem

alexkirsz commented Jul 10, 2023

stevedeighton commented Jul 10, 2023

stevedeighton commented Jul 10, 2023

gokulkrishh commented Jul 12, 2023 • edited Loading

gokulkrishh commented Jul 12, 2023

ctkc commented Jul 12, 2023

gokulkrishh commented Jul 12, 2023

stevedeighton commented Jul 12, 2023

louisthomaspro commented Jul 15, 2023 • edited Loading

keno-reloaded commented Jul 15, 2023

askinbilir commented Jul 15, 2023

IamSolaSholzy01 commented Jul 16, 2023

monzim commented Jul 16, 2023

piedrahitapablo commented Jul 16, 2023

acomanescu commented Jul 17, 2023

piedrahitapablo commented Jul 17, 2023

pawanrana1992 commented Jul 18, 2023

timneutkens commented Jul 18, 2023

dihan48 commented Jul 18, 2023

timneutkens commented Jul 18, 2023

julioflima commented Jul 18, 2023

khuezy commented Jul 19, 2023

timneutkens commented Jul 19, 2023

codeawy commented May 24, 2023 •

edited by shuding

Loading

leimonio commented Jun 9, 2023 •

edited

Loading

leimonio commented Jun 9, 2023 •

edited

Loading

darasus commented Jul 3, 2023 •

edited

Loading

stevedeighton commented Jul 3, 2023 •

edited

Loading

gokulkrishh commented Jul 12, 2023 •

edited

Loading

louisthomaspro commented Jul 15, 2023 •

edited

Loading