We might consider changing this default behavior in future, but for now, users have to manage their connection pool by passing us an agent explicitly.

Relevant spec: https://fetch.spec.whatwg.org/#connections

I agree that overriding global agent options causes unexpected behavior for NodeJS devs so getNodeRequestOptions should honor them. This is expecially true when you have to use node-fetch aside other http clients (ie. some cloud sdk) that you want to configure once.

I think #1736 kind of fixed this? At least the fact that the underlying keepAlive of the default agent was previously broken by explicitly setting Connection: close.

Or are there any other gotchas when patching the globalAgent?