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
npm proxy error #236
Comments
After extensive review, I'm having a hard time trying to understand if this is an issue with vagrant-proxyconf? I'm no expert with NPM and node and I'm afraid I cannot reproduce this issue without more information. FWIW, the reason I say it doesn't appear to be vagrant-proxyconf is because of these lines in your log file.
|
vagrant version is 2.2.14 |
Please provide a copy of your Vagrantfile. Also, please provide supporting documentation and a way to reproduce this. |
Vagrantfile is
the way to reproduce this.
|
Thank you for the info. Again, I'm not sure this is a bug in vagrant-proxyconf and after reviewing the code it appears it's been this way since 2014 and no code changes have been introduced to vagrant-proxyconf outside a formatting refactor. I cannot reproduce this error using
Also as stated before I'm not all that familiar with Node and NPM. It doesn't mean I won't help, it just means that since I'm a OSS developer I also rely on the community to help provide workarounds and or provide a good working example. For example on CentOS 7, npm is installed from EPEL and is version I'm just trying to help maintain this plugin. I'm not the original author of all the features this plugin supports. I'm just trying to do the best I can until Vagrant switches from ruby to GO. As of which time, I will no longer contribute to this plugin when it switches to GO. |
FWIW, I used the I'm not going to spend anymore time troubleshooting why NPM doesn't work. |
i try to set proxy for npm and i get this.
it's look's like proxy value must be full url ,so i try set proxy null ,and it worked.
|
Hi @bakeDong1 - Thank you for providing that information. I'll get back to you in a few days when I have some free time. |
Sorry, I've not had time to get to this like I hoped. I'll do my best and at lest provide a better status before the end of the week. |
Hey @codylane - sorry I haven't had time to help as much as I've wanted to. I think I can help with this, though. @bakeDong1 - This issue with You can verify yourself, too, by using # Install NVM (it'll tell you to open a new session/terminal after install)
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
### restart session / terminal ###
# Install and use latest stable node (16.4.2 as of now), which includes latest npm (7.18.1 as of now)
nvm install stable
# Watch noproxy fail...
npm config set noproxy foo
# npm ERR! obj[key].join is not a function...
# Install and use node 15.14.x which uses npm 7.15.1 as of now
nvm install 15.14
# Watch noproxy work as expected
npm config set noproxy foo
npm config ls | grep noproxy
# noproxy = ["foo"] From what I've read, installing older versions of things using From what I can tell this isn't really related to |
Right on @chucknelson, I appreciate the assist here and to provide some very helpful and accurate information. Major kudos. I hope you are well and thanks again for your help with this project. |
Closing per #236 (comment) |
when set npm proxy get error
and log is
is npm 1.7 change config noproxy format ?
The text was updated successfully, but these errors were encountered: