Rank, 14 days: 17 on the Next.js sheet
2 people reported

All time, since Oct 9.

Namespace re-exports not tree-shaken

“Turbopack ships lib/locales in the client bundle.”

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/10841/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 keeps unused members of re-exported namespaces. Unused modules reached through a namespace re-export ship in the client bundle with next build; next build --webpack leaves them out.

Is this your bug?

File my report
Where
Turbopack builds
Versions
16.3.3 to 16.5.0-canary.6
Platforms
macOS
How bad
Breaks a normal workflow.

Not quite your bug?

  1. Build hangs on worker import cycle3 people
  2. Loaders get stale file content2 people

Original reports2, newest first

  1. Turbopack: re-exported namespace (import * as x; export { x }) keeps every member, webpack tree-shakes itOn GitHub#101019
  2. Turbopack keeps unused exports of a namespace reached through another namespace (lib.core.X)On GitHub#99954

Do you work on Next.js?

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