0👍
✅
You may also be able to use a proxy definition in a
The issue, I suspect is that you’re installing from behind a VPN.
You can try disabling it to do the install
on corporate networks that’s not always the option
If you don’t have the option to disable…
you may be able to use
npm config set registry=http://registry.npmjs.org/
The reason that works is that you’re no longer connecting to the default which uses https
, where the SSL is failing due the the proxy.
Note that there is an issue of security if you opt to use http
instead of https
You may also be able to use a proxy definition in a .npmrc
file
If you have your proxy information, you can add it to the .npmrc
file in the directory.
https://docs.npmjs.com/misc/config#https-proxy
proxy http://{proxy_server}:{proxy_port}
https-proxy http://{proxy_server}:{proxy_port}
strict-ssl=false
Source:stackexchange.com