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
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Problem: VS Code has changed how the terminal is launched:
previously a node.js process with an identifying argument --type=terminal was used; now an executable winpty-agent.exe is used.
Since the auto-attach feature needs to identify this process, it was broken by the VS Code change.
The text was updated successfully, but these errors were encountered:
weinand
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Aug 2, 2018
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 issuesverifiedVerification succeeded
VS Code Insiders:
node --inspect test.js
Observe: debugger does not automatically attach
Problem: VS Code has changed how the terminal is launched:
previously a node.js process with an identifying argument
--type=terminal
was used; now an executablewinpty-agent.exe
is used.Since the auto-attach feature needs to identify this process, it was broken by the VS Code change.
The text was updated successfully, but these errors were encountered: