You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
use nvm which 7.10.1 to find the path to a node executable of a pre-8.0 version of node
create an npm script that uses this version of node, e.g. "debug": "/Users/weinand/.nvm/versions/node/v7.10.1/bin/node --debug-brk hello.js"
in npm script explorer select the new script and run the context menu action "Debug" on it
Observe: debugger times out after 10 seconds.
I've debugged this on the VS Code side and the problem is a missing "protocol": "legacy" attribute in the launch config passed to vscode.debug.startDebugging. Without that the debugger assumes the "inspector" protocol.
I suggest to always pass the "protocol" attribute. Use a value of "inspector" when detecting a "inspect" option and a value of "legacy" when detecting a "debug" option in the npm script.
The text was updated successfully, but these errors were encountered:
weinand
added
the
bug
Issue identified by VS Code Team member as probable bug
label
Apr 24, 2018
testing #48354:
nvm which 7.10.1
to find the path to a node executable of a pre-8.0 version of node"debug": "/Users/weinand/.nvm/versions/node/v7.10.1/bin/node --debug-brk hello.js"
Observe: debugger times out after 10 seconds.
I've debugged this on the VS Code side and the problem is a missing
"protocol": "legacy"
attribute in the launch config passed tovscode.debug.startDebugging
. Without that the debugger assumes the "inspector" protocol.I suggest to always pass the
"protocol"
attribute. Use a value of"inspector"
when detecting a "inspect" option and a value of"legacy"
when detecting a "debug" option in the npm script.The text was updated successfully, but these errors were encountered: