image-webpack-loader
image-webpack-loader copied to clipboard
tcoopman
Not working behind proxy
Our build server is behind a corporate proxy. This results in timouts when npm trying to install gifsicle, mozjpeg and so on, all used by image-webpack-loader.
I've read that this can be solved somehow by using https://github.com/kevva/bin-wrapper
Any idea on how to solve this?
Are you sure you need something like this? Isn't something like: https://jjasonclark.com/how-to-setup-node-behind-web-proxy/ enough?
On Thu, 12 Jan 2017 at 08:59 Christofer Hellqvist [email protected] wrote:
Our build server is behind a corporate proxy. This results in timouts when npm trying to install gifsicle, mozjpeg and so on, all used by image-webpack-loader.
I've read that this can be solved somehow by using https://github.com/kevva/bin-wrapper
Any idea on how to solve this?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tcoopman/image-webpack-loader/issues/65, or mute the thread https://github.com/notifications/unsubscribe-auth/AACx6pKtpKXC_0xPtP6OSWIT_xbVWl87ks5rRd1TgaJpZM4Lhd8J .
I will actually try that and see if it helps. Thanks, I get back to you with the result.
Any update on this? Currently only npmjs is trusted so it would be good if this works without using proxies on other websites which defeats the purpose of the firewall blocking.
