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

@instruments/taxonomy-client

v1.10.0

Published

Generated server-only TypeScript client for the public Taxonomy API.

Readme

@instruments/taxonomy-client

The generated, server-only TypeScript client for the public Taxonomy API. It contains transport code and OpenAPI-derived types only: it does not ship the Taxonomy corpus or depend on @instruments/taxonomy at runtime.

import { createTaxonomyClient } from "@instruments/taxonomy-client";

const taxonomy = createTaxonomyClient();
const result = await taxonomy.resolveTerm({
  path: { term: "walnut" },
  query: { context: "material" },
});

if (result.status === 200) {
  console.log(result.body);
}

The client exposes one method per canonical OpenAPI operationId: listAxes, getAxis, getConcept, getFacetedConcept, traverseGraph, getSnapshot, resolveTerm, and listTerms. Every method has generated request and status-discriminated response types. Problem responses use the generated TaxonomyProblemDetails type.

If the server returns a status that the operation does not document, the method rejects with TaxonomyUnexpectedResponseError instead of presenting that response as a member of the generated response union. The error exposes the operationId, numeric status, and original Response.

createTaxonomyClient is the only hand-written configuration seam. It accepts an optional baseUrl, fetch, and default headers. The package has a null browser export and refuses browser-like runtime evaluation; call it only from Node server code, server actions, route handlers, or other server-only modules.

Contract regeneration

The canonical contract remains packages/http-api/src/openapi.ts. After changing it, run:

pnpm --filter @instruments/taxonomy-client generate
pnpm --filter @instruments/taxonomy-client check:generated

The repository release gate checks exact generated output and runs a packed-tarball fresh-consumer smoke test before publication.