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

docshelf

v1.0.1

Published

A dead-simple documentation framework with minimal setup, beautiful design, and effortless deployment.

Downloads

292

Readme

docshelf

Static documentation from Markdown, with a small setup and output that works on any static host.

docshelf turns a folder of Markdown files into static HTML, CSS, JavaScript, search data, feeds, and metadata. The generated site does not need an application server.

Read the official documentation for the complete guide.

Installation

# Using Bun
bun add -d docshelf
# Using npm
npm install -D docshelf
# Using pnpm
pnpm add -D docshelf

Create a site

npx docshelf init
npx docshelf dev

init creates missing starter files. It keeps existing package.json, docs/, and docshelf.toml files, and adds a small .gitignore when needed.

The development server watches Markdown files, public/, and docshelf.toml. It ignores generated output, dependencies, and temporary files.

Commands

| Command | Purpose | | --- | --- | | docshelf init | Create missing starter files | | docshelf dev | Build, watch, and serve the site | | docshelf build | Generate static output in dist/ | | docshelf check | Validate frontmatter, links, assets, and components | | docshelf preview | Serve an existing dist/ folder |

Useful options:

npx docshelf dev --open
npx docshelf dev --port 4173 --host 127.0.0.1
npx docshelf build --base /my-repository
npx docshelf build --docs content --out public-site

For CI, use DOCSHELF_BASE, DOCSHELF_DOCS, DOCSHELF_OUT, DOCSHELF_PORT, or DOCSHELF_HOST. Command-line options take priority.

Project files

docs/
├── index.md
└── guides/
    └── install.md
public/
├── custom.css
└── images/
docshelf.toml

Markdown files become clean routes. docs/index.md becomes /, and docs/guides/install.md becomes /guides/install/.

Markdown

docshelf supports frontmatter, GitHub-flavored Markdown, tables, links, images, fenced code blocks, automatic syntax highlighting, and reusable blocks:

  • Callouts
  • Accordions
  • Tabs
  • Code groups
  • Cards
  • Tables
  • Steps
  • Version badges
  • Keyboard shortcuts
  • Image and video blocks

Example:

---
title: Getting started
description: Start here.
group: Start here
order: 1
---

::: tip title="One command"
Run `docshelf init` to create a starter site.
:::

Validation

Run the checker before publishing:

npx docshelf check

It reports invalid frontmatter, links to missing pages, missing local assets, missing branding assets, and unknown component names. External URLs are left alone.

Configuration

Use docshelf.toml for site-wide settings:

| Section | Purpose | | --- | --- | | [site] | Site name, description, and URL | | [announcement] | Optional sticky announcement | | [branding] | Header title and icon | | [theme] | Light, dark, or system mode | | [navigation] | Sidebar, breadcrumbs, table of contents, and page links | | [markdown] | Highlighting, line numbers, and heading anchors | | [search] | Generated client-side search index | | [seo] | Canonical links, JSON-LD, robots, and social metadata | | [validation] | Error, warning, or ignore behavior |

Use public/custom.css for colors and visual changes. Set branding.icon to a Phosphor icon name or an asset such as logo.svg from public/.

Deploy

Build the static site and upload dist/ to your host:

npx docshelf build

The output works with GitHub Pages, Cloudflare Pages, Netlify, S3, or a plain file server.

License

MIT. See LICENSE.