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
dbaeumer opened this issue
Sep 27, 2016
· 5 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Running npm run debug from the terminal works as expected.
I use nvm to manage my node installs. Don't know if this makes a difference.
The text was updated successfully, but these errors were encountered:
dbaeumer
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Sep 27, 2016
The problem is that on Windows both a 'npm' and a 'npm.cmd' exist on the PATH but only the latter actually works on Windows whereas the former is a shell script for linux/macOS. If a launch config specifies npm, VS Code will use the npm shell script which silently fails on Windows.
I've added this to the release notes.
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
Steps to Reproduce:
I use nvm to manage my node installs. Don't know if this makes a difference.
The text was updated successfully, but these errors were encountered: