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

@helping-ai-workflow/md2doc

v1.0.3

Published

Markdown → HTML / PDF renderer with WaveDrom, Mermaid, and Graphviz support

Readme

@helping-ai-workflow/md2doc

Markdown → HTML / PDF renderer with WaveDrom, Mermaid, and Graphviz support.

Two global CLIs (md2html, md2pdf) you can call from any directory.

Install

Requires Node.js 18 or higher. The first install pulls puppeteer (≈ 170 MB Chromium download); subsequent installs reuse it.

Recommended: install via nvm

If you do not yet have Node.js — or your system Node lives under /usr/local and npm install -g fails with EACCES — install Node through nvm first. nvm puts Node under ~/.nvm, so global packages never need sudo.

sudo apt install -y curl     # Debian / Ubuntu only; skip if curl is already installed
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/master/install.sh | bash
source ~/.zshrc              # or: source ~/.bashrc
nvm install --lts
nvm use --lts
npm install -g @helping-ai-workflow/md2doc

Already have Node.js

npm install -g @helping-ai-workflow/md2doc

Troubleshooting

EACCES: permission denied, mkdir '/usr/local/lib/node_modules' Your system Node is owned by root. Do not run sudo npm install -g — puppeteer's postinstall would download Chromium as root and break later runs. Instead, switch to nvm using the steps above.

Failed to set up chrome ...! Set "PUPPETEER_SKIP_DOWNLOAD" env variable to skip download. An earlier install left a half-finished Chromium download in ~/.cache/puppeteer. md2doc ≥ 1.0.3 cleans this automatically; on older versions, clear the cache and retry:

rm -rf ~/.cache/puppeteer
npm install -g @helping-ai-workflow/md2doc

Usage

md2html foo.md                     # → foo.html (next to source)
md2html foo.md bar.md              # batch render
md2html foo.md --out custom.html   # explicit output (single-file mode)
md2html foo.md --open              # render then launch viewer
md2html foo.md --quiet             # suppress progress output

md2pdf accepts the same four flags with PDF-output semantics.

Flags

| Flag | Meaning | |---|---| | --out <path> | Explicit output path. Only valid with exactly one input. | | --open | Launch the platform viewer (xdg-open / open / start) after render. | | --quiet | Suppress per-file progress messages. | | --version, -v | Print version. | | --help, -h | Print help. |

Supported diagram types

Embedded in fenced code blocks inside your Markdown:

```mermaid
graph LR
A --> B
```

```wavedrom
{ "signal": [...] }
```

```dot
digraph G { A -> B }
```

Diagrams render directly in the output (HTML or PDF).

Why a global CLI

Multiple repos used to ship copies of this script. They drifted. This package centralises the renderer so every repo references the same version. See docs/why.md for background.

Licence

MIT.