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 🙏

© 2025 – Pkg Stats / Ryan Hefner

trpc-openapi-2

v0.1.7

Published

Generate an OpenAPI spec from your tRPC server, in one line of code

Readme


Generate an OpenAPI spec from your tRPC server, in one line of code

Step 1: Install trpc-openapi-2

# npm
npm install trpc-openapi-2

# yarn
yarn install trpc-openapi-2

# pnpm
pnpm install trpc-openapi-2

Step 2: Generate OpenAPI spec

import { trpcToOpenApi } from "trpc-openapi-2";

// generate OpenAPI spec
const openApiSpec = trpcToOpenApi({
  apiTitle: "Your API",
  apiVersion: "1.0.0",
  basePath: "/trpc",
  router: trpcRouter,
});

// express example: serve openapi spec at /openapi.json
app.get("/openapi.json", (_, res) => res.json(openApiSpec));

Configuring the OpenAPI spec

Excluding certain procedures

Step 1: Add OpenApiMeta to your initTRPC call:

import { OpenApiMeta } from "trpc-openapi-2";

const t = initTRPC.meta<OpenApiMeta>().create();

Step 2: Use .meta() in your procedure

const router = t.router({
  myProcedure: t.procedure
    .meta({ openapi: { ignore: true } }) /* 👈 */
    .input(...
});

Comparison

trpc-openapi and its new fork trpc-to-openapi are the two relevant libraries.

They modify your API by adding new endpoints

These other libraries do not simply generate an OpenAPI spec for your existing tRPC server. They add new endpoints to your server and then generate an OpenAPI spec for those new endpoints.

For example:

// trpc-openapi example:

export const appRouter = t.router({
  sayHello: t.procedure

    // trpc-openapi adds a new endpoint to your server (`/say-hello`)
    // and the generated OpenAPI spec only includes this new `/say-hello`
    // endpoint, not the original `/trpc/sayHello` procedure
    .meta({ /* 👉 */ openapi: { method: "GET", path: "/say-hello" } }),
});

In comparison, trpc-openapi-2 simply generates an OpenAPI spec for your existing tRPC API, without modifying your API functionality at all.

They require you to use .meta() on every procedure

These libraries require that you add .meta() to every procedure that you want included in your OpenAPI spec. In comparison, with trpc-openapi-2 you can generate the full OpenAPI spec by calling trpcToOpenApi() without modifying your procedures at all.