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

@contract-first-api/openapi

v1.0.1

Published

Generate OpenAPI documents from contract-first API contract trees.

Downloads

157

Readme

@contract-first-api/openapi

Generate an OpenAPI document from a shared contract tree.

This package consumes contracts from @contract-first-api/core and turns them into a plain OpenAPI document object. It does not write files, register routes, serve Swagger UI, or choose a documentation frontend. You decide whether to write the document to disk, expose it from your backend, or pass it to another tool.

Install

pnpm add @contract-first-api/openapi

Create A Document

import { createOpenApiDocument } from "@contract-first-api/openapi";
import { contracts } from "@example/shared";

export const openApiDocument = createOpenApiDocument(contracts, {
	info: {
		title: "Todo API",
		version: "1.0.0",
	},
	servers: [{ url: "http://localhost:3000/api" }],
});

The returned value is a normal object. You can write it to a file:

import { writeFileSync } from "node:fs";
import { openApiDocument } from "./openapi.ts";

writeFileSync("openapi.json", JSON.stringify(openApiDocument, null, 2));

Or expose it from your backend:

app.get("/openapi.json", (_req, res) => {
	res.json(openApiDocument);
});

Contract Mapping

The generator walks the contract tree and creates one OpenAPI operation for each JSON contract.

  • path values like /todos/:id become /todos/{id}
  • method becomes the OpenAPI operation method
  • request.params becomes path parameters
  • request.query becomes query parameters
  • request.body becomes a JSON request body
  • response becomes the success response schema
  • successStatusCode becomes the success response status when provided
  • errors become additional response entries

Only JSON contracts are included in the generated document.

Zod JSON Schema

Schemas are converted with Zod 4's built-in z.toJSONSchema() support. Request schemas use input mode, and response schemas use output mode.

By default, unrepresentable Zod schemas throw during document generation. This keeps the generated document from silently describing something less precise than the contract.

createOpenApiDocument(contracts, {
	info: {
		title: "Todo API",
		version: "1.0.0",
	},
	schema: {
		unrepresentable: "any",
	},
});

Customizing The Document

Use transformOperation for route-level OpenAPI fields such as summary, tags, security, or vendor extensions.

const document = createOpenApiDocument(contracts, {
	info: {
		title: "Todo API",
		version: "1.0.0",
	},
	transformOperation: ({ contract, operation }) => ({
		...operation,
		...(contract.meta?.requiresAuth
			? { security: [{ bearerAuth: [] }] }
			: {}),
	}),
});

Use transformDocument for top-level fields and shared components.

const document = createOpenApiDocument(contracts, {
	info: {
		title: "Todo API",
		version: "1.0.0",
	},
	transformDocument: (document) => ({
		...document,
		components: {
			...document.components,
			securitySchemes: {
				bearerAuth: {
					type: "http",
					scheme: "bearer",
				},
			},
		},
	}),
});