Question 1

global-agent vs global-tunnel: which should I use for Node.js?

Accepted Answer

Use global-agent for Node.js v10+ as it avoids monkey-patching and uses modern APIs, while global-tunnel is for legacy versions below v10 with workarounds, as highlighted in the FAQ comparison.

Question 2

How to exclude domains from proxy in global-agent?

Accepted Answer

Set the GLOBAL_AGENT_NO_PROXY environment variable with comma-separated domain patterns like *.example.com, which allows direct connections to those URLs without proxying, as detailed in the 'Exclude URLs' section.

Question 3

Can I disable the agent override in global-agent?

Accepted Answer

Yes, set the GLOBAL_AGENT_FORCE_GLOBAL_AGENT environment variable to false, which stops global-agent from overriding explicitly configured agents, preventing conflicts with libraries that use custom agents.

Question 4

Does global-agent work with Node.js 8 or 9?

Accepted Answer

No, global-agent requires Node.js v10 or higher. For older versions, the README recommends alternatives like global-tunnel-ng, as shown in the conditional bootstrap example.

Question 5

How to set up a custom logger for debugging?

Accepted Answer

Provide a logger object with methods like debug and error when using createGlobalProxyAgent, allowing tailored logging for proxy activities, as specified in the API's custom logger section.

Question 6

What happens if I use both HTTP_PROXY and GLOBAL_AGENT_HTTP_PROXY?

Accepted Answer

By default, global-agent uses namespaced variables to avoid conflicts, but you can override this with GLOBAL_AGENT_ENVIRONMENT_VARIABLE_NAMESPACE to use standard HTTP_PROXY, as explained in the FAQ on environment variables.

global-agent

What is global-agent?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions