Security News
Highlights from the 2024 Rails Community Survey
A record 2,709 developers participated in the 2024 Ruby on Rails Community Survey, revealing key tools, practices, and trends shaping the Rails ecosystem.
node-fetch-native
Advanced tools
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')
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!
The npm package node-fetch-native receives a total of 4,848,574 weekly downloads. As such, node-fetch-native popularity was classified as popular.
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
A record 2,709 developers participated in the 2024 Ruby on Rails Community Survey, revealing key tools, practices, and trends shaping the Rails ecosystem.
Security News
In 2023, data breaches surged 78% from zero-day and supply chain attacks, but developers are still buried under alerts that are unable to prevent these threats.
Security News
Solo open source maintainers face burnout and security challenges, with 60% unpaid and 60% considering quitting.