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

@openapi-press/client

v0.1.1

Published

The wiring layer that turns spec descriptors into live, typed API clients.

Readme

@openapi-press/client

The wiring layer that turns spec descriptors into live, typed API clients.

The client model

An openapi-press client is a nested namespace tree of @openapi-press/spec descriptors bound to a transport. defineClient<paths>() binds the generated spec type once; its build(tree, config) walks the tree, replacing each descriptor leaf with an @openapi-press/call callable whose signature is derived from the spec — positional path params, query/body optionality, and the success payload type. Errors are never returned: every failure throws from the @openapi-press/error hierarchy.

The client stays focused on wiring: each invocation is a single transport attempt, observed by the hooks. Behavior — retry, timeouts, whatever an SDK author decides an endpoint needs — is applied per endpoint through the call's .with combinator; nothing is instrumented by default.

Configuration is two-tier. ClientConfig applies to every call a client makes (base URL, fetch, headers, logger, hooks, error mapping); CallConfig rides on an individual call's trailing options (signal, headers) and wins on conflict.

Usage

import { definePress } from "@openapi-press/client";
import type { paths } from "./schema.gen";

const { op, client } = definePress<paths>();

// A Press: minimal config in, usable client out. Export it — apps and
// integrations decide the config; the SDK owns the shape.
export const createApi = client({
  users: {
    list: op("get", "/users"),
    get: op("get", "/users/{user_id}"),
  },
});

const api = createApi({ baseUrl: "https://api.example.com" });
const user = await api.users.get("user-123");

The lower-level pieces remain available when a Press is not the right shape: defineSpec + defineClient().build(tree, config) compose the same client step by step, and endpoints can be instrumented per call site:

import { withRetry, withTimeout } from "@openapi-press/call";

const retry = withRetry();
const getUser = api.users.get.with(retry, withTimeout(5000));

API

  • definePress<Paths>() — the authoring kit: op for spec-checked descriptors, client(tree) to capture a tree into a Press<T> — the config-accepting client factory integrations consume.
  • defineClient<Paths>() — binds a generated paths type; returns a ClientBuilder whose build(tree, config?) turns a descriptor tree into a typed client.
  • makeClient(tree, config?) — binds a descriptor tree without the typed layer; the machine-facing counterpart to defineClient.
  • ClientConfig / CallConfig — the two configuration tiers.
  • Hooks — observe-only lifecycle hooks, firing around each transport attempt with the real Request/Response.
  • Bound<Paths, Tree> / BoundMethod<Paths, M, P> / CallOptions<Op> / OptionsArg<Op> — the call-signature composition over the spec's derived types.