nextjs - 💡(How to fix) Fix [Turbopack] Windows `next build` fails in standalone mode with `EINVAL: invalid argument, copyfile ... node:inspector` [1 comments, 2 participants]

Link to the code that reproduces this issue

https://github.com/example/sorry

To Reproduce

When running next build with output: "standalone" on Windows using Turbopack (default in Next.js 16+ or explicitly enabled), the build fails during the file copying phase.

It attempts to copy a traced file for the node:inspector module, but the destination filename contains a colon (:), which is invalid on Windows filesystems.

This issue persists even in Next.js 16.1.6, despite PR #88273 (escape colon in output names) being merged.

Current vs. Expected behavior

(

Provide environment information

1. Create a Next.js 16.1.6 project on Windows.
2. Enable `output: "standalone"` in `next.config.ts`.
4. Run `next build`.

Which area(s) are affected? (Select all that apply)

Output, Turbopack, Webpack

Which stage(s) are affected? (Select all that apply)

next build (local)

Additional context

No response