Closed jeffmaury closed 4 years ago
It’s not a limitation of the protocol.
Does the node debug adapter have some options to map local client-side vs remote/deployment URLs?
This can be closed as the vscode-nodedebugadapter has localRoot
and remoteRoot
parameters to handle this case.
Correct, either use the "localRoot" and "remoteRoot" attributes of the debug configuration for debug type "node" or just use the Remote Development extension.
In the future please only file bugs here if they are related to the three npm modules. File Debug Adapter Protocol issues here: https://github.com/microsoft/debug-adapter-protocol/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc
And VS Code/Node.js debugging related issues here: https://github.com/Microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc
I tried to debug a node based application running in a container through the attach mode and noticed that the breapoints are not supported (they are ignored). Is this a limitation of the Debug Adapter Protocol ? Or an issue in the Node adapter ?