Change NVM_NODEJS_ORG_MIRROR to NODEJS_ORG_MIRROR to solve npm install error
See original GitHub issuegyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:13 (4 by maintainers)
Top Results From Across the Web
NVM_NODEJS_ORG_MIRROR is deprecated, please use ...
I have nvm setup and when my npm pointer was on older node v4.4.0 I got the message warning ".... is deprecated, please...
Read more >Common errors | npm Docs
You are trying to install on a drive that either has no space, or has no permission to write. Free some disk space...
Read more >Resolving EACCES permissions errors when installing ...
Resolving EACCES permissions errors when installing packages globally · Reinstall npm with a node version manager · Manually change npm's default directory.
Read more >n - npm
If you already have Node.js installed, an easy way to install n is using npm : ... If the active node version does...
Read more >npm-install - npm Docs
Install a package. ... npm install (in a package directory, no arguments): ... does not exist in the registry data for that package,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I see - thanks for the clarification. I don’t use node-gyp directly, but
node-gyp rebuild
is run automatically when node.bcrypt.js is installed, which is when this warning is generated.It transpires that
nvm
sets theNVM_NODEJS_ORG_MIRROR
variable in the latest version of nvm.sh and, indeed,NODEJS_ORG_MIRROR
is not set.So, it seems like
bcrypt
isn’t going to install correctly whenNVM_NODEJS_ORG_MIRROR
is removed, and end-users will have to explicitly configureNODEJS_ORG_MIRROR
. It seems like a potentially unnecessary configuration step for a lot of people.If this is the case, is there anything that can be done to make it easier for those people? Do you think ‘nvm’ should set up the new variable in its script, or is there something
bcrypt
can do?It should, and - in newer releases - it will. We discussed it with the maintainer of nvm before putting in that change.