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

@cadelwatson/nanodoc

v0.1.1

Published

Literate documentation generator

Readme

nanodoc

Generate a single self-contained HTML document from source-code comments.

Requirements

  • Node.js 20+
  • Python on PATH (python or python3)

Install

npm install
npm run build

Usage

nanodoc <entrypoint>

Or with a config file:

nanodoc --config ./nanodoc.json

or during development:

npm run dev -- <entrypoint>

This writes <entrypoint-name>.html to the current working directory.

When using --config, each generated HTML file is written into the config's outputDir (created automatically if missing).

Config File

Use a JSON file with this shape:

{
  "entrypoints": ["./src/main.ts", "./src/guide.py"],
  "outputDir": "./docs"
}

Paths in entrypoints and outputDir are resolved relative to the config file.

Supported sources

  • TypeScript: .ts, .tsx
  • Python: .py

Included comment types

  • TypeScript: block comments (/* ... */, /** ... */)
  • Python: docstrings + # comment blocks opted in with @doc

Use @nodoc on the first line of an included comment to suppress it.

Features

  • Markdown rendering for extracted prose
  • First included comment first line becomes document <h1>
  • One-level appendix inclusion from Markdown links to source files
  • Mermaid fenced blocks (```mermaid)
  • Local Markdown images inlined as base64 data: URLs
  • Tufte CSS typography and layout styling
  • Single self-contained HTML output (inline CSS/JS/assets)