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

@tango-ts/openapi

v0.9.0

Published

OpenAPI schema generation for Tango routers and viewsets.

Readme

@tango-ts/openapi

Responsibility

OpenAPI 3.1 generation from Tango's declarative router/viewset/model/serializer metadata. This package turns registered ModelViewSet routes into paths, operations, request bodies, responses, and component schemas. It does not own routing or request handling.

What it responds to

  • A Router with registered routes.
  • ModelViewSet route metadata.
  • Model field specs and serializer field/read-only configuration.

Functionality

  • generateOpenApi(router, { title, version }).
  • generateOpenApi(project) defaults info.title from the project name and info.version to 0.0.0.
  • addOpenApiRoute(project, { path, title, version }) — serves the generated document from the project itself (default GET /openapi.json), generated lazily on first request and cached. This is what generated projects use.
  • Path generation for list/create/retrieve routes.
  • Path generation for custom ModelViewSet actions.
  • Component schemas inferred from model fields.
  • Input schemas that omit serializer read-only fields.
  • Per-operation overrides for parameters, request bodies, responses, tags, and operation IDs.

Design patterns that matter here

  • Declarative docs: no hand-written endpoint schemas for normal ModelViewSet routes.
  • Single source of truth: schemas derive from the same model and serializer config used at runtime.
  • Boundary with views: @tango-ts/views owns lightweight metadata and per-action override shapes; this package owns all OpenAPI document generation logic.
  • OpenAPI as verification: route/serializer/model declarations are introspectable, which will keep future API behavior honest.
  • Override escape hatch: overridden handlers/custom actions can still publish exact schema details without hand-writing the whole document.

Public contract

Everything exported from src/index.ts.

Testing

  • Unit (test/openapi.test.ts): path operations, operation IDs, path params, and component schemas derived from a registered ModelViewSet, including custom actions and view-specific OpenAPI overrides; addOpenApiRoute serving the document through the project handler at the default and custom paths.