[Turbopack] Windows next build fails in standalone mode with `EINVAL: invalid argument, copyfile .

[immiProgrammer]

Summary

Summary

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.

Reproduction Steps

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

Error Log

> Build error occurred
Error: EINVAL: invalid argument, copyfile 'D:\path\to\.next\server\chunks\[externals]_node:inspector_7a4283c6._.js' -> 'D:\path\to\.next\standalone\apps\web\.next\server\chunks\[externals]_node:inspector_7a4283c6._.js'
    at ignore-listed frames {
  errno: -4071,
  code: 'EINVAL',
  syscall: 'copyfile',
  path: 'D:\\path\\to\\.next\\server\\chunks\\[externals]_node:inspector_7a4283c6._.js',
  dest: 'D:\\path\\to\\.next\\standalone\\apps\\web\\.next\\server\\chunks\\[externals]_node:inspector_7a4283c6._.js'
}

Environment

• OS: Windows (10/11)
• Next.js: 16.1.6
• Package Manager: pnpm
• Turbopack: Enabled

Additional information

No response

Example

No response

[icyJoseph]

#88273 is still canary only. Try with next@canary to verify.

earliest canary was 16.1.1-canary.19

[immiProgrammer]

i need stable version 😁

[icyJoseph]

I said try canary to verify the fix. And then we wait until a new stable release. I haven't heard about a 16.1.7 just yet, but if I do I'll ask to include this PR on it.

[immiProgrammer]

i tested with 16.2.0-canary.45, fixed

[immiProgrammer]

Do you know which upcoming stable release will include this fix?
I’d like to plan our upgrade accordingly.