A proof-of-concept for migrating to native fetch. However, there are a few limitations today.

No native proxy support

It is possible to enable proxy support, however customers would have to install unidici downstream. Including it in this library would make it far too large. Here are some numbers:

Adding undici would double the size of a downstream dependency like @google-cloud/storage.

However, there is discussion on adding the ProxyAgent within Node:

• Expose Undici's ProxyAgent and setGlobalDispatcher within Node nodejs/node#43187

Workaround

Potential workaround/fallback for customers:

import {instance, request} from 'gaxios';
import {fetch, ProxyAgent} from 'undici';

instance.defaults.fetchImplementation = fetch;

await request({
  url: '', 
  dispatcher: new ProxyAgent();
})

Environment support

Additionally, it wasn't until recently that undici added env support for HTTP_PROXY, HTTPS_PROXY, & NO_PROXY and it will take time for it to propagate to Node.js releases:

• Added EnvHttpProxyAgent to support HTTP_PROXY nodejs/undici#2994
  • Available in: [Release] v6.14.0 nodejs/undici#3147
    • Landed in Node v22.3.0: https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V22.md#22.3.0

Performance

The native fetch implementation is 26% - 28% slower than node-fetch according to undici's benchmarks:

• https://github.com/nodejs/undici?tab=readme-ov-file#benchmarks
  • UPDATE: Fixed in Node 22+ fetch() performance parity nodejs/undici#1203 (comment), where it is roughly 42% faster than node-fetch

Returning Streams

Native fetch returns a ReadableStream ('Web Streams') instead of stream.Readable. This may require a rewriting downstream for many applications that currently expects a Node stream.

However, here's a simple way to resolve:

import {Readable} from 'node:stream';

Readable.fromWeb(res.body);

Additional Notes

https://nodejs.org/en/about/previous-releases

Fixes: #625
🦕