node v20, closing server and re-listening between requests causes ECONNRESET about node-fetch

[Moumouls]

My team encountered the same issue. In our test suite for impacted test we provided a new agent without keep alive.

Btw, think it's not really an issue of node-fetch, but a new behavior of Node 19 and 20. Since Node 19 the global default agent use keep alive.

The workaround is providing a custom agent for impacted test calls.

import { Agent } from 'http'
import fetch from 'node-fetch'

fetch(myUrl, { agent: new Agent() })

Technically this kind of issue should only occur in test purpose. Another solution is to change the port between each test.

[zalox]

I also encountered this bug now when attempting to do consecutive calls to an API. One workaround I found was to include a await new Promise(resolve => resolve(setTimeout)); before the await fetch. So there is probably a synchronization bug somewhere.

The same code base works as expected with node 18, so I switched to that for now.

[isaacs]

Technically this kind of issue should only occur in test purpose. Another solution is to change the port between each test.

If you make repeated requests to a server in production, and the connection closes between requests, it could happen in production as well. Servers do restart sometimes in real life.