Link to the code that reproduces this issue

https://github.com/emilioestebanez/next-15-issues

To Reproduce

1. Open in VSCode
2. Go to Run and Debug and execute the Next.js: debug server-side
3. Set a breakpoint in src/app/page.tsx
4. Visit http://localhost:3000

You'll see that the debugger doesn't stop in the breakpoint in Windows.

Now, if you go to package.json and remove --turbopack from the dev script and try the steps above again, you'll see that the debugger is able to stop in the breakpoint correctly.

This happens after next@15.0.3-canary.7

This has been tested also in 15.2.2 and it still doesn't work.

Current vs. Expected behavior

I expect the breakpoint to stop with and without --turbopack enabled.

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 65208
  Available CPU cores: 20
Binaries:
  Node: 20.18.0
  npm: 10.8.2
  Yarn: 1.22.22
  pnpm: 9.12.3
Relevant Packages:
  next: 15.0.3 // Latest available version is detected (15.0.3).
  eslint-config-next: 15.0.3
  react: 19.0.0-rc-66855b96-20241106
  react-dom: 19.0.0-rc-66855b96-20241106
  typescript: 5.7.2
Next.js Config:
  output: N/A

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

Turbopack

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

next dev (local)

Additional context

I think this is the cause of the issue:
#71984