Describe the Bug
Hey !
I’m a huge fan of Cursor, and i’m encountering on my work computer a bug I cannot fix … On VSCode, I’ve a launch.json configuration with two NodeJS processes, with env, etc, and a compound to start every service at the same time.
On VSCode, everything is working fine, VSCode can attach himself to the processes, breakpoints are working.
On Cursor, processes appear for one second in the process list, and disappear. 2/3 of time, process doesn’t start correctly, and when they are working fine, breakpoints doesn’t work.
Steps to Reproduce
Start node process with :
- request: launch
- runtimeExecutable: npm
- runtimeArgs: [“run”, “dev”]
- console: integratedTerminal
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.2.4 (user setup)
VSCode Version: 1.99.3
Node.js: 20.19.0
(Not complete, my work computer is … at work)
Does this stop you from using Cursor
No - Cursor works, but with this issue