-
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_CONFIG_PREFIX is ignored during install #4467
Comments
Do you mean NPM_CONFIG_PREFIX? NODE_CONFIG isn’t a thing. |
It looks like |
To clarify, I was able to reproduce the issue with the correct environment variable. |
Yes, thanks for picking that up. I used the wrong variable name in the bug description, but the bug is there with |
I've updated the text of the ticket for clarity: |
I see this is giving same result in both the latest as well as mentioned version(8.1.2), @chr15m let me know if you are still facing this. |
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
Trying to set the
prefix
config option using environment variables as documented here:https://docs.npmjs.com/cli/v8/using-npm/config#environment-variables
The current behaviour is that the output from these two commands is different.
In addition, currently this command:
does not install into the folder
dingle
whereas this command does:Expected Behavior
Expected behaviour setting the
prefix
via eitherNPM_CONFIG_PREFIX
or--prefix
has the same results and installs into the specified folder.Steps To Reproduce
$ npm --version
->8.1.2
NPM_CONFIG_PREFIX=dingle npm config ls -l | grep prefix
andnpm --prefix dingle config ls -l | grep prefix
Environment
The text was updated successfully, but these errors were encountered: