node-fetch does not work behind a proxy

[deeprobin]

Reproduction

Steps to reproduce the behavior:

1. Install some tooling which consumes the fetch api
2. Go behind some corporate proxy
3. Try to run

Expected behavior

If not explicitly specified, use of the system proxy.

Under Windows, for example, the proxy settings should be taken into account.
With more priority, the environment variables HTTP_PROXY, HTTPS_PROXY & NO_PROXY should also be taken into account.

Screenshots

Your Environment

software	version
node-fetch	^3.3.1
node	18.15.0
pnpm	7.30.0
Operating System	Microsoft Windows 10 Enterprise Version 22H2 (Build 19045.3208)

Additional context

[hinricht]

Looking forward to a solution, because it completely breaks the usage of many nodeJS apps which use node-fetch behind a proxy.

[hinricht]

@deeprobin Did you find any workaround for this ?

[deeprobin]

@deeprobin Did you find any workaround for this ?

@hinricht
Not yet. I have only seen that some tools do the proxy handling themselves and pass it to node-fetch.

In my opinion, this should be part of node-fetch.

[hinricht]

I just tried https://github.com/rofl0r/proxychains-ng and it solved at least my issue with https://github.com/todogroup/repolinter (which uses node-fetch internally).

[lselden]

I've been using global-agent with node-fetch for a while now (though on v2.7 and only for node < v18)

import * as globalAgent from 'global-agent';
process.env["GLOBAL_AGENT_HTTP_PROXY"] = process.env.HTTP_PROXY || "http://my.proxy.address:8888";
globalAgent.bootstrap();

[Vringe]

Just hit the same problem using live-plugin-manager. I also agree that this should be added to node-fetch instead of every project using node-fetch having to implement their own proxy handler.