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

docusite

v0.2.0

Published

Dead-simple documentation tool powered by VitePress

Readme

docusite

Dead-simple documentation tool powered by VitePress.

Quick Start

pnpm add -D docusite

Create docusite.config.ts in your project root:

import { defineConfig } from 'docusite'

export default defineConfig({
  title: 'My Project',
  description: 'Awesome project docs',
  logos: {
    main: '/public/logo.svg',
    hero: '/public/logo.svg',
  },
  colors: {
    light: '#646cff',
    dark: '#535bf2',
  },
  nav: [
    { text: 'Guide', link: '/guide/' },
  ],
  sidebar: {
    '/guide/': [
      {
        text: 'Guide',
        items: [
          { text: 'Getting Started', link: '/guide/getting-started' },
        ],
      },
    ],
  },
  search: 'local',
  llms: true,
  socialLinks: [
    { icon: 'github', link: 'https://github.com/user/repo' },
  ],
})

Add scripts to package.json:

{
  "scripts": {
    "docs:dev": "docusite dev",
    "docs:build": "docusite build",
    "docs:preview": "docusite preview"
  }
}

Create your docs:

mkdir -p docs/guide
echo '# Getting Started\n\nWelcome to the docs!' > docs/guide/getting-started.md
echo '---\nlayout: home\n---' > docs/index.md

Run the dev server:

pnpm docs:dev

Configuration

docsDir

Path to the docs directory (default: './docs').

title / description

Site title and description. Used in HTML <head> and the default theme.

logos

Site logos — paths relative to the docs directory, including public/ (file docs/public/logo.svg'/public/logo.svg'):

logos: {
  main: '/public/logo.svg', // navbar, next to the site title
  hero: '/public/logo.svg', // home page hero image
  favicon: '/public/logo.svg', // browser tab icon (optional; defaults to main)
  banner: '/public/banner.png', // Open Graph / Twitter card image
}
  • main — logo in the navbar next to the site title
  • hero — hero image on pages with layout: home (injected into frontmatter; falls back to main if omitted)
  • favicon — favicon for the browser tab (falls back to main if omitted)
  • banner — image for Open Graph / Twitter Cards (og:image, twitter:image); not set unless provided

Open Graph / Twitter Cards

When a site hostname is known (github or sitemap.hostname), docusite injects canonical, Open Graph, and Twitter Card meta tags into <head>. Image tags are added only when logos.banner is set.

colors

Brand colors for automatic CSS variable generation. Provide a light and/or dark hex color:

colors: {
  light: '#646cff',  // Used for :root (light theme)
  dark: '#535bf2',   // Used for .dark (dark theme)
}

Docusite auto-generates all VitePress brand CSS variables (--vp-c-brand-1, --vp-c-brand-2, --vp-c-brand-3, --vp-c-brand-soft, --vp-c-brand-dark, --vp-c-brand-dimm).

nav / sidebar

Standard VitePress navigation and sidebar configuration. See VitePress Default Theme Config.

locales

Multi-language support via VitePress i18n:

locales: {
  root: { label: 'English', lang: 'en' },
  ru: { label: 'Русский', lang: 'ru', link: '/ru/' },
}

Each locale can have its own nav and sidebar.

search

Search provider. Default is 'local' (MiniSearch). For Algolia:

search: {
  provider: 'algolia',
  options: {
    appId: 'YOUR_APP_ID',
    apiKey: 'YOUR_API_KEY',
    indexName: 'YOUR_INDEX_NAME',
  },
}

llms

Enable llms.txt and llms-full.txt generation (default: true). Disable with llms: false, or pass options:

llms: {
  ignoreFiles: ['private/**'],
  description: 'Custom description for llms.txt',
}

socialLinks

Social links displayed in the navigation bar.

head

Additional <head> tags (same format as VitePress).

customCss

Custom CSS file paths to inject.

themeConfigOverrides / siteConfigOverrides

Raw VitePress theme/site config overrides, merged last. Use these for any VitePress option not covered by docusite's config.

CLI

docusite dev [root]     # Start dev server
docusite build [root]   # Build for production
docusite preview [root] # Preview production build

Options:

  • --port <port> — Specify dev/preview server port

How It Works

Docusite reads your docusite.config.ts, transforms it into a VitePress configuration, writes it to .vitepress/config.mts inside your docs directory, and runs VitePress's programmatic API. The .vitepress/ directory is automatically added to your docs' .gitignore.

Requirements

  • Node.js >= 20
  • pnpm (recommended) or npm/yarn

License

MIT