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
[QUESTION] xxx is not a valid npm option #5852
Comments
I'm having a similar issue. |
No this was very much intentional and npm is going to be moving even further in the direction of not allowing invalid configs. None of these would be looked at by npm or any of its submodules anyways. |
Many NPM modules are using third-part URL for downloading something during installation. Currently these configurations are stored in NPM config file => not allow anymore these properties will add complexity in NPM configuration ("manipulate" file manually, environment variables, ...). I have in mind (
|
This broke our workflow, but since we needed only one npm config var, I just hijacked one that isn't particularly important to NPM: |
Have the same issue when I use |
Have you found an answer to that yet? I can't work without it. |
Also interested in a solution |
has anyone figured out the solution? |
I found the solution to my issue but it's difficult to articulate because it's been a while. If I remember right, it was an issue with read/write permissions of my drive where I had my projects. So in |
For those still searching for a solution; i worked 'around it' by including a .npmrc with the keys already in there. So i was using:
And now I'm using a .npmrc file with:
And then in the step:
|
That's a pretty stupid change, CI pipelines are not working now because many dependencies use variables that we neep to set into the npm config (.npmrc) Needing to update the .npmrc with bash script when npm config exist is really annoying... |
How do I change distUrl in npm ? what's solution here? |
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
Running
npm config -g test-key test-value
and I get:I am sad with this change since all custom configs cannot be set by running
npm config
. And is there any plans to remove this limit?Expected Behavior
npm config works fine while using custom config
Steps To Reproduce
Just run
npm config
with custom config:npm config -g set <custom-key> <custom-value>
Environment
The text was updated successfully, but these errors were encountered: