node-fetch polyfill causes indefinitely pending promises when using the retry middleware about wretch-middlewares HOT 2 CLOSED

Hey @NetroScript,

I think that the issue could be related to the way node-fetch implements response cloning which is used under the hood by the retry middleware.

Could you try to increase the highWaterMark as described in their documentation?

https://github.com/node-fetch/node-fetch#custom-highwatermark

from wretch-middlewares.

This does indeed fix the problem.

But should someone in the future also have the same problem I will also describe the solution I now have:

I am using TypeScript and I am using commonjs. This means I couldn't import node-fetch@3 the default way (due to it not working with require in the TS output) and was just using version 2 before. (But version 3 is needed as only starting with that version highWaterMark was added).

To be able to use version 3 with my setup, I had to use the following code in my async bootstrapping function:

async function bootstrap() {
  // If NodeJS supports the fetch function, we do not need to import it
  if (typeof fetch == 'undefined') {
    const _importDynamic = new Function(
      'modulePath',
      'return import(modulePath)',
    );
    const { default: fetch } = await _importDynamic('node-fetch');
    global.fetch = fetch;
  }
  ....
}

bootstrap();

And the final function looking like this works without problems:

    const data = await wretch(
      url,
      {
        highWaterMark: 1024 * 1024,
      },
    )
      .middlewares([retry()])
      .get()
      .json();

from wretch-middlewares.