-
Notifications
You must be signed in to change notification settings - Fork 58
Can't hit early breakpoints when debugging with --experimental-modules and .mjs #158
Comments
From @ThePlenkov on December 9, 2017 11:49 What is interesting. If to put breakpoint into the classic JS module it stops there. And then you can go back. But in this case you have a different file: In this file you can already set breakpoints. |
There are two issues with this:
|
From @ThePlenkov on December 10, 2017 0:43 @roblourens the problem is that VS Code debugger even doesn't The workaround now is like this: It automatically starts chrome dev tools with my mjs module. (NIM extesnsion do the magic) So finally I develop in VS Code and debug in Chrome. I find a very valuable feature opportunity to debug mjs directly from VS Code. |
That's because we start Node in a paused state, then attach. Right now it will skip right over the debugger statement before we are able to attach. Debugging in Chrome devtools should give a similar experience except for #157. I will move this bug to the right repo and keep it open to track the upstream issue in Node. |
Node 9.6.0 solves this issue. Request that this issue be closed |
Thanks |
From @ThePlenkov on December 9, 2017 9:7
Hi,
I hope I chose the correct place to create the issue.
I'm trying to debug mjs node file but the breakpoints are just ignored.
Please see attached gif file.
![2017-12-09_10-04-31](https://user-images.githubusercontent.com/6381507/33794258-850f6f4a-dcc8-11e7-91a9-56a77046060b.gif)
This is my configuration:
Do I do something wrongly or it's just not supported yet?
Thank you!
Copied from original issue: microsoft/vscode-node-debug#167
The text was updated successfully, but these errors were encountered: