Hi @thgreasi, @balena-ci

I've encountered severe memory issues with fetch-ponyfill in our Node.js server that have caused multiple memory-related restarts.

I would find if very helpful to use the native fetch version as it would allow me to use node-fetch v3 when operating in Node 20 or node 22, v3 has improved streaming handling capabilities which I believe would reduce the memory related issues I am seeing.

As fetch-ponyfill uses node-fetch ~2.6.1 regardless of which node environment you are operating on, by using it I am unable to gain the benefits of native node fetch in node 20 or 22

{"callFrame":{
  "functionName":"",
  "url":"/app/node_modules/fetch-ponyfill/node_modules/node-fetch/lib/index.js",
  "lineNumber":269
},
"selfSize":8389272}

Please let me know if you would like more details

Hi,
@Benedict-Carling that's the first time I hear about balena-request causing memory issues, so thanks for raising it.
I do want to get #185 to the finish line for sure. Code wise & as far I was able to test it with the balena-sdk & balena-cli it seems fine, but for some strange reason I'm facing issues with the tests failing. More interestingly running the tests in isolation works, but running them all together is when it fails, and at the same time the were passing for node 18 just fine.
I can't dedicate time on this right now, but I will raise this internally.

@thgreasi Thank you for your response, I'm happy to have a look at the tests myself when I get time