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
In node v6 the stack trace request fails for callbacks which results in an empty call stack view in the VS Code debugger. Oddly enough VS Code's code injection fixes the failing stacktrace request for yet unknown reasons.
Until VS Code 1.1.1 code injection was only working for a debug session of type 'launch'. As a consequence node v6 debugging would fail in debug sessions of type 'attach'. In the May milestone we've fixed code injection for 'attach' mode which makes node v6 debugging work in VS Code 1.2 in 'attach' mode.
Verify that you can attach to and debug an express application:
install node v6
from command line
run npm install -g express-generator
generate express application with express myExpressApp
run cd myExpressApp
run npm install
run node --debug bin\www
open myExpressApp with VS Code and attach to the node process
Test for #6029:
In node v6 the stack trace request fails for callbacks which results in an empty call stack view in the VS Code debugger. Oddly enough VS Code's code injection fixes the failing stacktrace request for yet unknown reasons.
Until VS Code 1.1.1 code injection was only working for a debug session of type 'launch'. As a consequence node v6 debugging would fail in debug sessions of type 'attach'. In the May milestone we've fixed code injection for 'attach' mode which makes node v6 debugging work in VS Code 1.2 in 'attach' mode.
Verify that you can attach to and debug an express application:
npm install -g express-generator
express myExpressApp
cd myExpressApp
npm install
node --debug bin\www
myExpressApp
with VS Code and attach to the node processindex.js:line:6
Verify that the call stack view shows the stack trace correctly.
The text was updated successfully, but these errors were encountered: