1 person reported

All time, since Oct 12.

webpackChunkName ignored

“Build with pnpm build (Turbopack) and observe that the chunk name is lost 💥”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/next-js/issues/11843/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Turbopack ignores webpackChunkName comments on dynamic imports. After switching from webpack builds, named chunks like video-player.<hash>.js become generated filenames such as 1a9ut2wf58r-n.js.

Is this your bug?

File my report
Where
Turbopack build
Versions
16.4.0
Platforms
macOS
How bad
Breaks a normal workflow.

Original reports2, newest first

  1. Turbopack: webpackChunkName ignored when migrating from webpackOn GitHub#100051
  2. Turbopack: webpackChunkName ignored when migrating from webpackOn GitHub#100050

Do you work on Next.js?

Claim its RAP Sheet to see what your users report and answer them in one place.