Fetcher

Convenient wrapper around fetch.

Features

• Works in the Browser and on the Server (Node.js)
• Convenient API, e.g fetcher.get(), fetcher.post(), etc.
• Throws HttpError automatically, no need to check if (res.ok)
• Allows to set timeout
• Conveniently retries on retry-able errors
• Allows to conveniently log requests/responses, configurable
• Allows to convert searchParams object into a query string
• Allows to define beforeRequest/beforeRetry/afterResponse hooks

Comparison

Fetcher:

const fetcher = getFetcher()

const result = await fetcher.post('https://example.com', {
  json: { foo: true },
})

Ky:

const result = await ky
  .post('https://example.com/hello', {
    json: { foo: true },
  })
  .json()

Plain fetch:

class HTTPError extends Error {}

const response = await fetch('https://example.com', {
  method: 'POST',
  body: JSON.stringify({ foo: true }),
  headers: {
    'content-type': 'application/json',
  },
})

if (!response.ok) {
  throw new HTTPError(`Fetch error: ${response.statusText}`)
}

const json = await response.json()

console.log(json)

Prior art

Heavily inspired by:

• ky, ky-universal
• node-fetch
• got
• axios
• getGot (nodejs-lib)
• getKy (frontend-lib)

Why

Differences from prior projects:

• Targets both Browser and Node by design, targeting Node with native fetch support. This is similar to ky plus ky-universal.
• Incorporates everything from getKy and getGot, so you don’t need multiple layers. For example, with ky you would need: ky, ky-for-people, getKy (frontend-lib). With fetcher you need only fetcher (part of js-lib).

Goals

• Simplicity. It focuses on the most simple and common use cases, and not on the most advanced or edge cases.
• Assume native fetch support (Browser and Node), no polyfills. Should work equally well in Browser and Node, ideally without platform-specific quirks.
• Written in TypeScript, with first-class TypeScript support.