node-fetch-native is a Node.js fetch implementation intended to provide better backward and forward compatibility by redistributing node-fetch v3 (and more). It offers CommonJS and ESM usage, prefers native fetch when available, and includes proxy support (via HTTP Agent or Undici Proxy Agent) for environments that need HTTP proxy handling.
Project status
- The repo appears actively maintained, with an upstream GitHub push timestamp today (2026-06-09), though the most recent tagged update in the provided history is v1.6.7 dated 2025-08-02.
- Update cadence looks occasional and uneven, with the last two tagged updates close together in Jan 2025 (v1.6.5 and v1.6.6), then a longer gap until Aug 2025 (v1.6.7), and earlier gaps of roughly many months between minor/patch updates.
AI summary generated
Recent updates
v1.6.7
Release v1.6.7 mainly changes the build output target to ES2020. The repository also updates its lockfile and bumps development toolchain dependencies, but those additional changes are not described in the provided release notes.
Breakingv1.6.6
v1.6.6 updates node-fetch-native with a small runtime-warning improvement and a dependency adjustment to use undici v6. It also refactors how the `fetch` and `Blob` exports are selected at module load time.
v1.6.5
v1.6.5 is described in the release notes as a dependency-only release. The diff confirms broad dependency and tooling updates, plus some lint configuration and minor code style changes, with no explicit API documentation changes.
v1.6.4
Release v1.6.4 is described as a build/export change, specifically removing a `node > require` conditional export for the `./proxy` subpath. The code diff mainly updates `package.json` export conditions, with some additional changelog and version-related edits.
Breakingv1.6.3
The v1.6.3 release notes only mention a generic dependency update. The code diff indicates a large dependency churn in the lockfile and some tooling/version bumps in package metadata, with at least one build-related change referenced in the changelog content that is not mentioned in the v1.6.3 release notes.
v1.6.2
v1.6.2 release notes describe a build-related fix that removes an invalid `node.import` export condition, plus a dependency update. No functional or API behavior changes are explicitly documented beyond the build/export metadata adjustment.
Breakingv1.6.1
v1.6.1 is a small patch release focused on the proxy module's CommonJS (CJS) build behavior. The code change primarily reorders exports in src/proxy.ts to resolve a CJS build issue, without changing the proxy API implementation.
v1.6.0
v1.6.0 adds proxy support exports for `fetch` and `createFetch`, and extends proxy configuration to respect `no_proxy`/`NO_PROXY` (and a `noProxy` option). It also changes how proxy environment variables are selected (including lower-case variants). The code changes include additional behavioral tweaks not covered in the release notes.
Featuresv1.5.1
The release notes for v1.5.1 claim a proxy-related fix (supporting lower-case environment variables) and a types-only change for the /proxy subpath export. However, the actual diff provided does not show any proxy or type implementation changes, and instead only updates CHANGELOG.md and package.json metadata.
v1.5.0
This release adds HTTP proxy support to node-fetch-native by introducing a new `createProxy` helper that returns either a Node.js HTTP/S agent (`agent`) and/or an Undici `dispatcher` for native fetch scenarios. The codebase also updates build and package export mappings to ship a new `node-fetch-native/proxy` entrypoint and includes a basic test that exercises the proxy configuration.
Features