npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

flyreq

v0.1.0

Published

FeiFly flyreq — single-package frontend request library with swappable transports

Readme

flyreq

Layered frontend request library with swappable transports. This is the umbrella package — install it alone and you get the core, the business protocol layer, the fetch/xhr transports and the codegen CLI.

pnpm add flyreq

Usage

import { setupFlyreq, flyreq } from 'flyreq'

setupFlyreq({
  baseURL: 'https://api.example.com',
  token: () => localStorage.getItem('jwt') ?? '',
})

const user = await flyreq.get<User>('/user/1')
await flyreq.post('/order', payload, { idempotent: true })

setupFlyreq is the composition root: it configures the business protocol and injects a transport. After that you only touch flyreq.get / post / put / patch / delete / head / options.

Call options

| Option | Meaning | |--------|---------| | retry | Retry network errors, 5xx and 429. true, a count, or full options | | cache | Cache successful responses only. true, a TTL in ms, or full options | | idempotent | Deduplicate concurrent identical requests (double-click safe) |

Transports

fetch (default) and xhr are built in. axios lives behind a subpath so it stays out of bundles that never use it — a static import would add ~48 kB to every consumer:

import { setupFlyreq } from 'flyreq'
import { createAxiosRequestor } from 'flyreq/axios'

setupFlyreq({ baseURL, backend: createAxiosRequestor() })

Using backend: 'axios' by name (including via flyreq.config.json) needs the adapter registered first:

import { registerAxiosAdapter } from 'flyreq/axios'

registerAxiosAdapter()

Any object satisfying Requestor works too, so you can bring your own transport with setBackend(myRequestor) or registerAdapter(name, factory).

Entry points

| Import | Contents | |--------|----------| | flyreq | Runtime API. Free of Node built-ins, safe for browser bundles | | flyreq/axios | axios transport, opt-in | | flyreq/node | Reads flyreq.config.json. Node/SSR only | | flyreq (bin) | flyreq gen codegen, flyreq use transport selection |

CLI

flyreq gen ./api.json -o ./src/generated
flyreq use fetch

License

MIT