Debugging mocha tests doesn't seem to work anymore.

[TwitchBronBron]

Using the latest version of this repo, when I try to debug a test using the "Current TS Tests File" configuration, it doesn't hit breakpoints set in typescript.

VSCode info
Version 1.22.0-insider
Commit a716373aaaf50cbce3618688a645b324721b35dd
Date 2018-03-14T05:15:41.910Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

[Neutrino-Sunset]

I see the same thing.

VSCode info
Version 1.21.0
Commit 9a199d77c82fcb82f39c68bb33c614af01c111ba
Date 2018-03-07T11:04:09.886Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture ia32

C:_Home\Development\Workspaces\NodeTesting\vscode-ts-node-debugging>node --version
v8.10.0

[dupski]

D'oh, sorry to hear this folks, sounds like node / MS have changed something again :)

Fix contributions welcome. I'll try to take a look at this at the weekend if I have time.

[Neutrino-Sunset]

I'd be eternally grateful if you could. I've spent days trying to come up with an effective Typescript test approach that doesn't require having to re-transpile the world on every modification and so far nothing works.

[KevinSnyderCodes]

I am having this issue on Windows 10, but not on macOS 10.13.3, both running the same version of:

• Node.js (7.9.0 in VS Code, 9.7.1 on the OS)
• ts-node (4.1.0)
• Mocha (5.0.0)

VS Code version is off by one patch (1.21.1 on Windows, 1.21.0 on macOS).

[k2snowman69]

I tagged a bug in Microsoft/vscode's issue list, if you do start investigating, that maybe a good place to start. Looks like several people are hitting some issues with ts-node and vscode.

[k2snowman69]

Summary:
Summary - this was broken by #43959, there is one case where the adapter doesn't correctly fix the drive letter case. I have a low-impact fix, everyone please try it in tomorrow's Insiders build (or the next vscode-chrome-debug update) and let me know how it goes.

@TwitchBronBron - Since you're already on the insider builds, mind giving this a try tomorrow? I'm on production builds and would rather not switch if someone already has their environment setup.

[TwitchBronBron]

@k2snowman69, that appears to be working now. I can set breakpoints in the source code and most of them work. However, it's skipping the first few breakpoints. I added another line to the top to try to see if it just didn't like to break at npm imports, but it skips that line too for some reason.

When I start debugging, this is the first line it hits.

VSCode info
Version 1.22.0-insider
Commit 9160e85b1ab0333dfe697032f90da494f1f81fd4
Date 2018-03-16T06:17:01.718Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

[k2snowman69]

Ha I guess that's a start! They said it was a targeted fix. Here is the thread about the fix where vscode requested for people to let them know how it goes... maybe share your result there. microsoft/vscode#45657 (comment) @k2snowman69<https://github.com/k2snowman69>, that appears to be working now. I can set breakpoints in the source code and most of them work. However, it's skipping the first few breakpoints. I added another line to the top to try to see if it just didn't like to break at npm imports, but it skips that line too for some reason. When I start debugging, this is the first line it hits. [image]<https://user-images.githubusercontent.com/2544493/37517721-b0f65684-28e8-11e8-847a-f74413f2e3d1.png> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#9 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADVECS_Fn2UtwBzHGr6l_3Xa9JtVeSOqks5te500gaJpZM4Sqm-W>.

[lostfields]

In the latest Insider running extension "Node Debug" > v1.22.4 it works for me

[renehauck]

In my case, sometimes he stop at a breakpoint, sometime he doesn't stop.
Additional, sometimes he jump back to an breakpoint.

VSCode info
Node-Debug 1.24.2
Commit dbf4d8b
Node 10.1.0
Architecture x64
OS Ubuntu