-
Notifications
You must be signed in to change notification settings - Fork 3.4k
[BUG] Powershell npm run parameters are lost #5435
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
Labels
Comments
Duplicate of #3136. |
Closed by #8278 (semver 7.7.2) |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
I print process.argv in powershell,use npm it will lose the parameter
--debug
,But pnpm won'ta.js
When I use pnpm run the result is correct, but with npm run I need to use --- or quotes,
Expected Behavior
No response
Steps To Reproduce
No response
Environment
The text was updated successfully, but these errors were encountered: