-
Notifications
You must be signed in to change notification settings - Fork 320
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
push not working through proxy #91
Comments
Done a bit of research into this and it looks like node's http doesn't really support proxies. I'll do some more research into it and let you know but I'm not that hopeful. |
Will be interesting to see what you come up with, normally node would use either the environment variables for HTTP_PROXY or HTTPS_PROXY, or the npm config setting for http-proxy or https-proxy. That's how I've got everything else working through the proxy but for some reason rollup doesn't seem to use the same settings. |
I'm having same issue on a corporate laptop and it's a huge bummer that I cannot use this as main dev station and have to use much worse personal laptop :( |
I believe this would be more accurately described as an improvement for the |
When I try to push I get this error:
node:744) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): FetchError: request to https://screeps.com:443/api/user/branches? failed, reason: read ECONNRESET
I can only assume this is because I am behind a proxy, is there any way of adding proxy info to the config file to allow this to work?
The text was updated successfully, but these errors were encountered: