Security News
The Push to Ban Ransom Payments Is Gaining Momentum
Ransomware costs victims an estimated $30 billion per year and has gotten so out of control that global support for banning payments is gaining momentum.
node-fetch-native
Advanced tools
Changelog
Readme
A redistribution of node-fetch v3 for better backward and forward compatibility.
Why this package?
require('node-fetch')
with latest version. This stopped popular libraries from upgrading and dependency conflicts between node-fetch@2
and node-fetch@3
.fetch
is being supported. We are prepared for native fetch support using this package yet keep supporting older Node versions.Features:
✅ Prefer to native globals when available (See Node.js experimental fetch).
✅ Compact build and less install size with zero dependencies vs
✅ Support both CommonJS (require
) and ESM (import
) usage
✅ Use native version if imported without node
condition using conditional exports with zero bundle overhead
✅ Polyfill support for Node.js
Install node-fetch-native
dependency:
# npm
npm i node-fetch-native
# yarn
yarn add node-fetch-native
# pnpm
pnpm i node-fetch-native
You can now either import or require the dependency:
// ESM
import fetch from 'node-fetch-native'
// CommonJS
const fetch = require('node-fetch-native')
More named exports:
// ESM
import { fetch, Blob, FormData, Headers, Request, Response, AbortController } from 'node-fetch-native'
// CommonJS
const { fetch, Blob, FormData, Headers, Request, Response, AbortController } = require('node-fetch-native')
Sometimes you want to explicitly use none native (node-fetch
) implementation of fetch
in case of issues with native/polyfill version of globalThis.fetch
with Node.js or runtime environment.
You have two ways to do this:
FORCE_NODE_FETCH
environment variable before starting application.node-fetch-native/node
Using the polyfill method, we can once ensure global fetch is available in the environment and all files. Natives are always preferred.
Note: I don't recommand this if you are authoring a library! Please prefer explicit methods.
// ESM
import 'node-fetch-native/polyfill'
// CJS
require('node-fetch-native/polyfill')
// You can now use fetch() without any import!
node-fetch
Using this method, you can ensure all project dependencies and usages of node-fetch
can benefit from improved node-fetch-native
and won't conflict between node-fetch@2
and node-fetch@3
.
Using npm overrides:
// package.json
{
"overrides": {
"node-fetch": "npm:node-fetch-native@latest"
}
}
Using yarn selective dependency resolutions:
// package.json
{
"resolutions": {
"node-fetch": "npm:node-fetch-native@latest"
}
}
Using pnpm.overrides:
// package.json
{
"pnpm": {
"overrides": {
"node-fetch": "npm:node-fetch-native@latest"
}
}
}
Made with 💛
FAQs
better fetch for Node.js. Works on any JavaScript runtime!
We found that node-fetch-native demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Ransomware costs victims an estimated $30 billion per year and has gotten so out of control that global support for banning payments is gaining momentum.
Application Security
New SEC disclosure rules aim to enforce timely cyber incident reporting, but fear of job loss and inadequate resources lead to significant underreporting.
Security News
The Python Software Foundation has secured a 5-year sponsorship from Fastly that supports PSF's activities and events, most notably the security and reliability of the Python Package Index (PyPI).