Turbopack Error: failed to write to E:\resonance\.next\dev\server\chunks\ssr\[externals]_node:inspector_7a4283c6._.js.map

[Shaffan23]

Turbopack version: 23c46498
Next.js version: 0.0.0

Error message:

failed to write to E:\resonance\.next\dev\server\chunks\ssr\[externals]_node:inspector_7a4283c6._.js.map

Caused by:
- The file or directory is corrupted and unreadable. (os error 1392)

[KartikSharma4448]

The important detail is Windows OS error 1392, which means ERROR_FILE_CORRUPT: a file or directory is corrupted and unreadable. This is different from a normal permissions error. It does not, by itself, prove that the whole drive is failing. Microsoft reference

I would investigate the filesystem before changing application code:

1. Stop the dev server and back up your source files.
2. Check whether File Explorer can access the affected directory under E:\resonance\.next.
3. If accessible, rename the generated .next folder to a backup name and restart so Next.js creates fresh output. Do not delete your source or lockfile.
4. If Windows cannot access or rename that folder, or the error recurs, investigate the volume's filesystem health rather than repeatedly clearing caches. Back up important data before attempting repairs.
5. Try a fresh checkout on another known-good local drive to help isolate the storage location.

Please also provide npx next info and the full error log. The reported Next.js version: 0.0.0 is insufficient to identify the installed release.

Webpack can be a comparison test, but switching bundlers will not repair an underlying filesystem problem.

[ExeDevCentral]

Following up on the colon hypothesis: the failing path is [externals]node:inspector_7a4283c6..js.map. On Windows, : is a reserved character in file names, and on NTFS name:stream is treated as an alternate data stream. So the write may fail because of the output file name, not because of disk corruption. Error 1392 would then be a misleading symptom.

Minimal repro to confirm (any drive, including C:):

Create a fresh app on Windows.
Import any node: builtin from server code (e.g. import "node:inspector").
Run next dev (Turbopack) and check whether it writes [externals]_node:*.js.map under .next\dev\server\chunks\ssr.

If it reproduces on C: with a clean project, this is a Turbopack bug: it should sanitize : in emitted chunk/source map file names on Windows.

Workarounds meanwhile:

next dev --webpack
Avoid importing node:-prefixed modules in the affected code path (use the unprefixed name if possible)

@Shaffan23, could you share npx next info, the filesystem type of E: (fsutil fsinfo volumeinfo E:), and whether it also fails on C:? That would separate the two causes.