Loaders get stale file content

“The first call gets the file's previous content, although the file on disk already has the new content.”

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/4180/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 loaders run on a file's previous content. Happens after editing a file in next dev or after a persistent build-cache restore; stateful loaders like @tailwindcss/turbopack ship stale CSS.

Is this your bug?

File my report

Where: Turbopack loaders
Versions: 16.3.6 to 16.5.0-canary.15
Platforms: Linux, macOS
How bad: Breaks a normal workflow.

Not quite your bug?

Build spawns a webpack-loader pool per loader chain and context9 people
Font fallback face dropped1 person
Nested next/dynamic CSS missing1 person

Original reports2, newest first

Oct 16, 2026Turbopack: after a persistent build-cache restore, webpack loaders run on the previous build's file content, and stateful loaders ship itOn GitHub#100326
Sep 27, 2026[turbopack] after a file changes, loaders are first run with the file's previous contentOn GitHub#99313

Loaders get stale file content

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

Is this your bug?

Not quite your bug?

Original reports2, newest first

Do you work on Next.js?