Rank, 14 days: 15 on the Next.js sheet
1 person reported
All time, since Nov 2.
Slow Turbopack production build
“On a mid-sized app, next build (Turbopack) is about 30× slower on 16.4.x than on 16.3.8, and the problem is already fixed on the 16.5 canary line.”
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/24157/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 production build compile far slower on 16.4.x. The compile step of next build uses all cores for about a minute, then runs a long single-threaded tail.
Is this your bug?
File my report- Where
- next build
- Versions
- 16.4.4
- Platforms
- Linux, Windows
- How bad
- Breaks a normal workflow.
Not quite your bug?
Original reports2, newest first
- Turbopack 16.4.x:
next buildcompile is 10-15x slower than on 16.3.8 / 16.5 canary with a barrel thatexport *s thousands of modulesOn GitHub#101045 - Turbopack production build: "Compiled successfully" takes 6–8 min on 16.4.x vs 15 s on 16.3.8 and 12 s on 16.5.0-canary.36 (same app, 3k modules)On GitHub#101039