Closed trs123 closed 4 years ago
This might be related to https://github.com/avh4/binwrap/pull/19#issuecomment-636322664
elmi-to-json@1.3.0 uses binwrap@0.2.2, which uses the npm request
package for HTTP. So you should be able to set environment variables as described here: https://github.com/request/request#controlling-proxy-behaviour-using-environment-variables
For example:
HTTPS_PROXY="https://USERNAME:PASSWORD@10.0.0.1:8080/" npm i elmi-to-json
Does something like that work?
The environment variables https_proxy
and http_proxy
had been set already but it seems that our VPN has changed (not sure if that is just an intermediate state or if it will stay that way), so I do not need to set them anymore and installing now works fine.
I am quite confused now because I'm not sure when that happened and so cannot reproduce the original error anymore.
Sorry about that. I'll close the issue for now and will reopen it if/when I encounter it again.
Hi, when trying to install elmi-to-json (for elm-spa) from behind a corporate firewall I get the following binwrap-install error:
This only happens for binwrap-install. Other packages not using it can be installed without problems, so it is not a problem with my proxy settings. It seems that binwrap-install does not honor the proxy settings.