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
roblourens opened this issue
Apr 12, 2017
· 1 comment
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesimportantIssue identified as high-priority
The --inspect --debug-brk option works from Node 6.3 through 7.x. The --inspect-brk option works from 7.6.0 through 8.x. --debug-brk was just removed: nodejs/node#12197. Hopefully it will be put back for backwards compatibility - nodejs/node#12364. Otherwise, VS Code 1.11 won't be able to debug Node 8 which is an issue.
The text was updated successfully, but these errors were encountered:
roblourens
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
important
Issue identified as high-priority
labels
Apr 12, 2017
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesimportantIssue identified as high-priority
microsoft/vscode-node-debug2#99
The
--inspect --debug-brk
option works from Node 6.3 through 7.x. The--inspect-brk
option works from 7.6.0 through 8.x.--debug-brk
was just removed: nodejs/node#12197. Hopefully it will be put back for backwards compatibility - nodejs/node#12364. Otherwise, VS Code 1.11 won't be able to debug Node 8 which is an issue.The text was updated successfully, but these errors were encountered: