You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
You might want to take this over to node-gyp – it does its own network fetches to download the Node package tarball from nodejs.org / iojs.org so it can extract the heards. I'm not really sure what support for proxying or nonstandard requests it has, but it's sort of a symbiote that tags along for the ride with npm. It's possible that npm's not passing along the correct configuration information to node-gyp, though, in which case this would be a bug in npm, so let us know if that's what they tell you.
We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining package.community and asking your question there.
For more information about our new issue aging policies and why we've instituted them please see our blog post.
My .npmrc looks like this:
It shouldn't even try to open a SSL connection because I'm using HTTP for the registry.
npm install protractor
gives an error when running node-gyp "Error: self signed certificate in certificate chain":The text was updated successfully, but these errors were encountered: