Description
- I don't see the node-proxy-agent dependency registered in package.json. Is this truly the HTTP client framework that corepack uses to download components when running
corepack install? - node-proxy-agent is a dead project with a successor "proxy-agents". When can we replace the dead proxy dependency with a live one?
- Despite both corepack and node-proxy-agent documenting uppercase
HTTP_PROXY,HTTPS_PROXYenvironment variables, on my machine only the lowercase oneshttp_proxy,https_proxyhave any effect on whether package installation occurs through a proxy or not. - Unlike many other applications, including NPM, corepack fails when presented with the proxy URL's
http://orhttps://(no address). The user's intention here is to indicate that no proxy should be used. And these URL values make larger configuration scripting a lot easier. - Why not use the same HTTP client as NPM, so that proxy configuration at least behaves identically? Then any questions about configuration can simply link to official NPM documentation. Smaller technology stack, smaller attack surface, less maintenance.
Metadata
Metadata
Assignees
Labels
No labels