Build hangs on worker import cycle

“Current: next build with Turbopack hangs silently.”

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/4131/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

Fading. No reports and thumbs-up in the last 7 days and 1 the week before, down from 2 a week at the late-September peak. A workaround is known.

Turbopack build hangs when worker imports its spawning module. next build never returns after "Creating an optimized production build ..." with 0% CPU and no error; webpack builds succeed.

Is this your bug?

File my report

Where: Turbopack build
Versions: 16.2.10 to 16.5.0-canary.9
Platforms: macOS
How bad: Breaks a normal workflow.

Not quite your bug?

Turbopack worker fails to load2 people
Page module factory not available20 people
Build spawns a webpack-loader pool per loader chain and context9 people

Original reports3, newest first

Oct 13, 2026Turbopack: next build hangs (0% CPU, no error) when a Web Worker's module graph imports the module that spawns itOn GitHub#100131
Oct 2, 2026Turbopack: next build hangs (0% CPU, no error) when a Web Worker's module graph imports the module that spawns itOn GitHub#99593
Oct 2, 2026Turbopack: next build hangs (0% CPU, no error) when a Web Worker's module graph imports the module that spawns itOn GitHub#99592