mcpField
U
upfetch

upfetch

github.com/l-blondyDevelopment1.4k43 installsUpdated 8w ago
Repository

About upfetch

upfetch is a guide to using a reusable fetch client, for TypeScript developers who need request defaults, validation, and lifecycle handling. It covers request and response shaping, retries, timeouts, and hooks, with further references organized by topic.

Key features

  1. 01Set dynamic request-scoped defaults
  2. 02Shape authentication, parameters, and request bodies
  3. 03Validate data at runtime with schemas
  4. 04Configure response parsing and error handling
  5. 05Handle retries, timeouts, and lifecycle hooks

Use cases

  1. 01Reuse base URLs and headers across API requests
  2. 02Validate the structure of server responses
  3. 03Add retry and timeout behavior to requests

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/l-blondy/up-fetch --skill upfetch

After installing, type/upfetchin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
auth-and-request-shaping.md
client-setup-and-dynamic-defaults.md
retries-timeouts-and-lifecycle.md
streaming-and-runtime-caveats.md
validation-parsing-and-errors.md

Details

From the project README

upfetch

Use up-fetch when you need a reusable fetch client with request-scoped defaults, automatic request/response shaping, runtime validation, retries, and lifecycle hooks.

Mental model

  • up(fetchFn, getDefaultOptions?) creates the reusable client.
  • getDefaultOptions(input, options, ctx) runs on every request.
  • upfetch(input, options?, ctx?) performs one request.
  • Keep SKILL.md high-level; load the relevant file under references/ for details.

Minimum pattern

import { up } from 'up-fetch'
import { z } from 'zod'

export const upfetch = up(fetch, () => ({
   baseUrl: 'https://api.example.com',
   headers: {
      Authorization: readToken() ? `Bearer ${readToken()}` : undefined,
   },
   timeout: 5000,
}))

const user = await upfetch('/users/1', {
   schema: z.object({
      id: z.number(),
      name: z.string(),
   }),
})

Workflow

  1. Start with client setup and dynamic defaults.
  2. If the request needs auth, params, body shaping, or merge semantics, read auth and request shaping.
  3. If the response contract matters, read validation, parsing, and errors.
  4. If retries, timeouts, or hook timing matter, read retries, timeouts, and lifecycle.
  5. If streaming or runtime quirks matter, read streaming and runtime caveats.

High-value rules

  • Pass a function as the second argument to up(), not a plain object.
  • Read auth and other mutable defaults inside that function so values stay fresh.
  • Use params and body instead of hand-serializing query strings or JSON.
  • Use schema when you need runtime trust; TypeScript generics alone do not validate payloads.
  • If you want error-as-value behavior, set reject: () => false before relying on parseResponse.
  • Prefer globalThis.fetch over imported undici.fetch.

References

Comments

Markdown supported