Swap proxy-agent
with https-proxy-agent
to defeat legacy ftp
package issue
#43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A fix for #42 - where the
ftp
package is causing the following warning when this package is used:Some investigation/further digging - the existing
proxy-agent
package simply wraps a number of packages for HTTP proxies, socks proxies/pac/etc. - but all we really need/want isHTTPS_PROXY
support.Thus, we can swap this out for the child
https-proxy-agent
package - and avoid bringing along all the cruft of additional packages we don't need - and in that, the offendingftp
package. 🎉.Have tested locally using Proxyman and
HTTPS_PROXY="http://127.0.0.1:9090"
- can see successful requests being made via Proxyman as the proxy.