-
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
node-gyp does not honor npm's cafile config #843
Comments
Fixed in 8c4b0ff which was released in v3.3.0 in February. Node.js v4.4.3 and v5.10.0 were the first releases to carry that version. |
If it's a command line option, then it's not going to work for multiple developers on the same project with different configs. Can we get it to respect an environment variable and/or npm's config where it's already set? |
@coke That's been the case since day one, see the linked commit log. |
For posterity/people who don't want to click the link: export npm_config_cafile=/path/to/ca.crt |
sigh. I swear I tried that env var last night; in the harsh light of the morning, It works fine. Thank you very much for your patient reply. |
Extremely odd to have a lower case env var like that |
You can also do: export NPM_CONFIG_CAFILE=/path/to/ca.crt |
See this persistent issue: nodejs/node#3742
The text was updated successfully, but these errors were encountered: