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

hono-autopenapi

v0.1.1

Published

Generate OpenAPI schema by statically analyzing Hono routes and c.json response types.

Readme

hono-autopenapi

Generate OpenAPI schema by statically analyzing Hono routes and the types passed to c.json().

Install

bun install

Build

bun run build

CLI

node ./dist/cli.js --entries "src/**/*.ts" --out openapi.json

Flags:

  • --entries Glob(s) for source files (default: src/**/*.ts)
  • --out Output file (default: openapi.json)
  • --root or --autoroutes Path to autoroutes root (e.g. src/routes). When provided, any matched route.ts inside this folder will have its local paths prefixed with the folder structure. Example: src/routes/users/route.ts with app.get('/:id', ...) becomes /users/:id.
  • --autorouter Path to autorouter root (e.g. src/app/(routes)). File- and folder-based routing like Next.js:
    • Folders form the base path.
    • Dynamic segments: [id] -> :id, [...slug] -> :slug.
    • index.ts contributes no segment, while get.ts/post.ts/etc. map methods but still need handlers discovered in code.
    • The analyzer prefixes discovered Hono route paths with this base.

Programmatic API

import { analyzeFilesToOpenAPI } from 'hono-autopenapi'

const openapi = await analyzeFilesToOpenAPI(['src/**/*.ts'])
console.log(JSON.stringify(openapi, null, 2))

With autoroutes/autorouter support:

import { analyzeToOpenAPI } from 'hono-autopenapi'

// autoroutes (route.ts under folders)
const openapiA = await analyzeToOpenAPI({
	entries: 'src/routes/**/route.ts',
	autoroutesRoot: 'src/routes',
})

// autorouter (folder-based like Next.js)
const openapiB = await analyzeToOpenAPI({
	entries: 'src/app/**/*.{ts,tsx}',
	autorouterRoot: 'src/app',
})

Notes

  • MVP focuses on responses returned via c.json(...) in route handlers like app.get('/path', (c) => c.json({...})).
  • Types are inferred via TypeScript's type checker; common primitives, arrays, and object shapes are supported.
  • Future: components $ref dedup, nested router composition, deeper Zod/TS coverage.

Built-in Docs Route (/docs)

Expose Swagger UI and your OpenAPI JSON with a single helper.

import { Hono } from 'hono'
import { mountDocs } from 'hono-autopenapi'

const app = new Hono()

// Option A: Provide an OpenAPI document directly
mountDocs(app, {
	document: {
		openapi: '3.1.0',
		info: { title: 'My API', version: '1.0.0' },
		paths: {}
	},
})

// Option B: Generate from source entries (supports autoroutes root)
mountDocs(app, {
	entries: 'src/**/*.ts',
	root: 'src/routes',
	docsPath: '/docs',
	jsonPath: '/openapi.json',
	title: 'My API',
	refreshOnRequest: process.env.NODE_ENV !== 'production',
})

export default app

Routes:

  • GET /openapi.json — serves the OpenAPI document
  • GET /docs — serves Swagger UI that loads /openapi.json