make-fetch-happen

Install cost

What you actually take on by adding make-fetch-happen to a project.

Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.

Compatibility

Node.js

node ^22.22.2 || ^24.15.0 || >=26.0.0

Module format

CommonJS only

TypeScript

No bundled types

Install scripts

None

Quick start

A usage example from the make-fetch-happen README.

const fetch = require('make-fetch-happen').defaults({
  cachePath: './my-cache' // path where cache will be written (and read)
})

fetch('https://registry.npmjs.org/make-fetch-happen').then(res => {
  return res.json() // download the body as JSON
}).then(body => {
  console.log(`got ${body.name} from web`)
  return fetch('https://registry.npmjs.org/make-fetch-happen', {
    cache: 'no-cache' // forces a conditional request
  })
}).then(res => {
  console.log(res.status) // 304! cache validated!
  return res.json().then(body => {

make-fetch-happen vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

Dependencies

Declared by make-fetch-happen v16.0.1. Runtime dependencies are installed with the package; dev dependencies are not.

Used by

Popular packages that depend on make-fetch-happen.

Relationship graph

Dependencies (left) and dependents (right) of make-fetch-happen.

Frequently installed together

Release history

12 releases in the last two years, typically about 30 days apart.

Overview

make-fetch-happen is an npm package that opinionated, caching, retrying fetch client. It is extremely widely used, with about 43.3M downloads per week and 1 known dependents in the graph. The latest version is 16.0.1, released under the ISC license.

Auto-generated from collected registry metadata. No external claims are inferred.

Frequently asked questions