npm installer fails on proxy and certificates

[catinthetap]

npm installer fails on proxy and certificates

[JordyMoos]

This worked for me
NODE_TLS_REJECT_UNAUTHORIZED="0" npm install -g elm

[haplesshero13]

We need a way to work around a corporate firewall as well. If there were a way to provide a custom binary host URL, that would be great for us. Otherwise, we'll have to hack a bunch of other packages that require a elm as an NPM dependency.

[dkowis]

The system has all the necessary certs installed to allow things to work with our Corporate MITM proxy here, but for some reason, this operation does not use those certificates, and so I also had to disable the TLS verification :(

The right solution is to fix the install.js so it honors system certificates.

[process-bot]

Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!

Here is what to expect next, and if anyone wants to comment, keep these things in mind.

[catinthetap]

JordyMoos suggestion of using NODE_TLS_REJECT_UNAUTHORISED="0" works fine but a) it seems like more of a work-around than a fix and b) I couldn't find it on the npmjs.com page for Elm. I'm concerned it will put off people less obsessive than me! ;-)