-
Notifications
You must be signed in to change notification settings - Fork 30.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't stop on breakpoints #45448
Comments
I have the same issue using sourcemaps and ts-node |
I've been having the same problem with TypeScript Mocha tests on Windows 10. It's very annoying. |
Can one of you share your project or some sample code? Or, please set |
I am having this issue with ts-node as well, not using any source maps on disc. Debugging up to 1.20 was always fine, now breakpoints are never hit. @roblourens You can find a repro project here |
@roblourens I've attached my debugadapter.txt. Hope it helps. |
@jugglingthebits I meet the problem with ts-node too when updating to 1.21. |
add property to launch.json, should fix it. |
@taosdc I can confirm that that fixed the problem for me. Thank you so much! |
This is probably #45657 (comment), please see the comment there and try in the next Insiders build. |
Hi everybody, Im having the same problem with ts using the VS code from version 1.19 to 1.21.1 |
Issue Type: Bug
Set a breakpoint and run. It does not stop anymore. I believe 1.20 and earlier worked, but not in 1.21.
This happens when running a test suite via jest is against code using TypeScript (v2.7.2) and using
ts-jest
(v21.2.4).We use the following setting to start the app:
When it starts it shows the following:
As soon as I change
sourceMaps
to false, then it works but it is not perfect as when it stops I do not get the yellow arrow telling me on which breakpoint it actually stopped and the step by step or step into functionality do not work at all or partially.VS Code version: Code 1.21.0 (9a199d7, 2018-03-07T11:04:09.886Z)
OS version: Windows_NT ia32 10.0.16299
System Info
|Process Argv|C:\Program Files (x86)\Microsoft VS Code\Code.exe|
|Screen Reader|no|
|VM|0%|
The text was updated successfully, but these errors were encountered: