-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Installing node v5.2.0 .node-gyp v3.0.3 latest version will not install behind proxy. Works with 0.12. #845
Comments
Any answers to this? My project is in danger now because company is not going to change their proxies and firewalls for me. |
Not really, although the next release will respect the
node-gyp tries to download the SDK from nodejs.org. If it can't punch through your firewall, download the appropriate source tarball from https://nodejs.org/dist/ and point npm / node-gyp to it with the EDIT:
That suggests your proxy uses e.g. 1024 bits certificates or an outdated cipher; v0.12 accepts those, v4.x and v5.x do not. |
I am using node v4 for now. As per your suggestion I downloaded node v4 tarball and tried installing and get the error below. Am I missing a step? --Thanks!
|
Ok, changed to command to the one below. Looks like contextify has issue. (I even upgraded node to version 5 of node and reinstalled node-gyp). Do I need to also do something else?
|
Make sure you download the source tarball, the binaries-only tarball doesn't include the SDK. Aside, you shouldn't need contextify in v5.x; the module has been integrated into the built-in |
Contextify is an older jsdom dependency requirement. Changed to newer version which does not have it as dependency and it worked. |
Cannot install modules with node v5.2.0 .node-gyp v3.0.3 behind the proxy with my configurations below. I've tried setting strict-ssl=false. same issue.
This same configuration/installation works perfect with 0.12 of node/npm 2.xxx.. Please help! I am stuck.
The text was updated successfully, but these errors were encountered: