-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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 run env echo
stopped working after 8.13
#5729
Comments
npm run env echo
stopped working between 8.12 and 8.18npm run env echo
stopped working between 8.12 and 8.13
npm run env echo
stopped working between 8.12 and 8.13npm run env echo
stopped working after 8.13
Looks like #5064 started quoting/escaping environment variable params too aggressively. If I run |
this is behaving as intended. when an argument is passed to a run-script the goal is to ensure that end script sees the exact input the user provided, and does not unexpectedly execute code. unfortunately what you were doing was taking advantage of the lack of escaping we had in the past, so now that the arguments are actually being escaped it no longer works. we do not intend to revert this behavior. as a workaround, you have a few options though.
|
@nlf |
This has broken our build -- it seems other package content like |
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
On
npm 8.12.1
I was runningnpm -s run env echo '$npm_package_version'
to get current package.json version. It does not work anymore. There are no traces of changes regarding that in https://github.com/npm/cli/blob/v8.19.2/CHANGELOG.mdExpected Behavior
Steps To Reproduce
No response
Environment
The text was updated successfully, but these errors were encountered: