-
Notifications
You must be signed in to change notification settings - Fork 97
Cannot debug mjs modules #167
Comments
There are two issues with this:
|
@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 microsoft/vscode-node-debug2#157. I will move this bug to the right repo and keep it open to track the upstream issue in Node. |
This issue was moved to microsoft/vscode-node-debug2#158 |
Worth noting that the "runtimeArgs" parameter is not documented at the obvious point in the documentation, https://code.visualstudio.com/docs/editor/debugging#_launchjson-attributes I ended up having to find this bug report to figure out that that parameter exists. I'll see if i can figure out where to properly report that, or fix it if the docs are publicly editable. |
That section doesn't list all attributes for Node debugging, just a few that are common among different debug adapters. There's a more exhaustive list of Node-specific launch config attributes here https://code.visualstudio.com/docs/nodejs/nodejs-debugging |
Seems that it might be good to have a list of all of the launch.json attributes in a place marked "launch.json attributes" ;-) But if debug adapters can use whatever they want, then that's difficult i guess. |
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.
This is my configuration:
Do I do something wrongly or it's just not supported yet?
Thank you!
The text was updated successfully, but these errors were encountered: