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

typespec-openapi-document

v0.4.0

Published

TypeSpec emitter: export the OpenAPI document @typespec/openapi3 writes as a typed module, with the import resolved for you, framework-agnostic, so you can serve it from anything.

Readme

typespec-openapi-document

Import your OpenAPI document as a typed TypeScript module, so you can serve it from your app.

@typespec/openapi3 writes the document; this generates the module that imports it, with the path worked out for you. Use it with any framework.

Install

pnpm add -D typespec-openapi-document

Peer dependencies: @typespec/compiler, @typespec/openapi3. @typespec/versioning is an optional peer, behind a guarded import, so a spec declaring no versions does not need it installed.

# tspconfig.yaml
emit:
  - "@typespec/openapi3"
  - typespec-openapi-document
options:
  "@typespec/openapi3":
    emitter-output-dir: "{project-root}/openapi"
    file-type: json # required, see below
  typespec-openapi-document:
    emitter-output-dir: "{project-root}/src/generated"

Quick start

You write two files. src/generated/document.gen.ts is produced by the compiler and never edited:

main.tsp                        your API definition
tspconfig.yaml                  which emitters to run
openapi/openapi.json            written by @typespec/openapi3
src/
  generated/
    document.gen.ts             written by this emitter, never edited by hand
  index.ts                      your app

tspconfig.yaml

emit:
  - "@typespec/openapi3"
  - typespec-openapi-document
options:
  "@typespec/openapi3":
    emitter-output-dir: "{project-root}/openapi"
    file-type: json
  typespec-openapi-document:
    emitter-output-dir: "{project-root}/src/generated"
pnpm exec tsp compile .

src/generated/document.gen.ts

Generated. One per @service:

import document from "../../openapi/openapi.json" with { type: "json" };

export const openApiDocument = document;
export const OPENAPI_DOCUMENT_PATH = "/openapi.json";

src/index.ts

Serve it with whatever you already use. This example is Hono, but nothing here is Hono-specific:

import { swaggerUI } from "@hono/swagger-ui";
import { Scalar } from "@scalar/hono-api-reference";
import { openApiDocument, OPENAPI_DOCUMENT_PATH } from "./generated/document.gen.js";

app.get(OPENAPI_DOCUMENT_PATH, (c) => c.json(openApiDocument));
app.get("/docs", swaggerUI({ url: OPENAPI_DOCUMENT_PATH }));
app.get("/reference", Scalar({ url: OPENAPI_DOCUMENT_PATH }));

Both of those take a URL and peer-depend on hono alone, so no code-first generator is involved.

The document is imported rather than read from disk, so it is part of your bundle. It cannot go stale relative to the build, and a missing one fails the build rather than a request. Measured on a 580-operation service: 517 KB raw, 9.7 KB gzipped, against a Cloudflare Worker's 3 MB budget.

Docs

  • Guides: versioned services, and why file-type: json is required
  • Reference: every option and every diagnostic

Licence

MIT.