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

@kagal/build-tsdoc

v0.1.0

Published

TSDoc extraction hook for unbuild

Downloads

303

Readme

@kagal/build-tsdoc

TSDoc extraction hook for unbuild. Extracts documented symbols from each entry point at build time and writes per-export api_<name>.json files plus a unified api.json manifest.

Usage

import { newDocumentsHook } from '@kagal/build-tsdoc';
import { defineBuildConfig } from 'unbuild';

export default defineBuildConfig({
  entries: [
    { input: 'src/index', name: 'index' },
    { input: 'src/types/index', name: 'types' },
    { input: 'src/schema/index', name: 'schema' },
  ],
  hooks: {
    'build:done': newDocumentsHook(),
  },
});

By default, output goes to _docs/ at the package root (not inside dist/, so it does not ship to npm). To override:

newDocumentsHook({ outputDirectory: 'docs/api' })

Output

For a package with index, types, and schema entries:

_docs/
  api.json          # unified manifest
  api_index.json    # symbols from src/index
  api_types.json    # symbols from src/types/index
  api_schema.json   # symbols from src/schema/index

Per-export files each contain a DocEntry[] array from tsdoc-markdown. The unified api.json manifest wraps them with package name, version, generation timestamp, and per-export metadata. The api_ prefix on per-export files keeps them in a separate filename namespace from the manifest, so packages whose exports include ./api do not collide with api.json.

Exports

| Export | Description | Deps | |--------|-------------|------| | @kagal/build-tsdoc | newDocumentsHook(), DEFAULT_OUTPUT_DIRECTORY, types, VERSION | tsdoc-markdown, unbuild (peer) |

Licence

MIT