Skip to content
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

Closed
mschnee opened this issue Dec 15, 2015 · 7 comments
Closed

node-gyp does not honor npm's cafile config #843

mschnee opened this issue Dec 15, 2015 · 7 comments

Comments

@mschnee
Copy link

mschnee commented Dec 15, 2015

See this persistent issue: nodejs/node#3742

@bnoordhuis
Copy link
Member

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.

@coke
Copy link

coke commented Jun 26, 2017

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?

@bnoordhuis
Copy link
Member

@coke That's been the case since day one, see the linked commit log.

@gibfahn
Copy link
Member

gibfahn commented Jun 26, 2017

For posterity/people who don't want to click the link:

export npm_config_cafile=/path/to/ca.crt

@coke
Copy link

coke commented Jun 26, 2017

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.

@factoidforrest
Copy link

Extremely odd to have a lower case env var like that

@gibfahn
Copy link
Member

gibfahn commented Jul 10, 2018

Extremely odd to have a lower case env var like that

You can also do:

export NPM_CONFIG_CAFILE=/path/to/ca.crt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants