next.js: [Windows] Server-side debugger doesn't stop in breakpoints after v15.0.3-canary.7
Link to the code that reproduces this issue
https://github.com/emilioestebanez/next-15-issues
To Reproduce
- Open in VSCode
- Go to
Run and Debugand execute theNext.js: debug server-side - Set a breakpoint in
src/app/page.tsx - 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: https://github.com/vercel/next.js/pull/71984
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 19 (4 by maintainers)
I am on Next 15.2.2 and the problem is not fixed.
Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!
same issue here. any solution for this?
Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!
I’m having the same issue. VScode won’t hit breakpoints when using turbo.
Same here, in Next.js 15.2.2 the same issue happens.
Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!
If someones is going here, update your next version to 15.2!!
On that version problem is fixed
I am also facing the problem of unbound breakpoints in Visual Studio Code. I am using Yarn.
Output of
next info:Relevant scripts section of in package.json:
Relevant launch configuration in Visual Studio Code:
Whenever I switch back to the normal dev server (without Turbopack, so
next dev), breakpoints are being bound and hit.@Falven , for me it fails with both npm and pnpm.
Updated the repo with next 15.1.0, and unfortunately the same issue happens.