-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] npm should use PowerShell by default on Windows #2699
Labels
Enhancement
new feature or improvement
platform:windows
is Windows-specific
Release 7.x
work is associated with a specific npm 7 release
Comments
Stanzilla
added
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 7.x
work is associated with a specific npm 7 release
labels
Feb 14, 2021
nlf
added
Enhancement
new feature or improvement
platform:windows
is Windows-specific
and removed
Bug
thing that needs fixing
Needs Triage
needs review for next steps
labels
Feb 16, 2021
changing the default shell would constitute a breaking change so this is unlikely to happen in npm 7 without further discussion. you might consider putting this suggestion through our rfc process, described here: https://github.com/npm/rfcs#rfc-process |
Closing, as per nlf's comments. This would need to be an RFC to change the default like this, and would also be a breaking change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Enhancement
new feature or improvement
platform:windows
is Windows-specific
Release 7.x
work is associated with a specific npm 7 release
The problem here is that cmd does not work with a few things that are now part of a Windows developer's daily workflow, like using WSL and it's network shared file system. cmd does not understand UNC file paths and therefore npm is broken by default when you first try to use it. Yes the default shell and default script shell can be changed but there is no reason why the default should still be cmd in the first place, imo.
Current Behavior:
npm on Windows uses the old cmd instead of PowerShell
Expected Behavior:
npm should use PowerShell by default
Environment:
The text was updated successfully, but these errors were encountered: