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

@supaproxy/supadocs

v0.2.0

Published

Opinionated docs framework. MDX in, beautiful site out.

Readme

supadocs

Opinionated docs framework. MDX in, beautiful site out.

  • Dark/light themes out of the box
  • Built-in components: callouts, cards, tabs, steps, accordions, code groups
  • Cmd+K search across all pages
  • Landing page with cards
  • Full theme customisation
  • Any Lucide icon by name
  • Zero config in your project. Just MDX files and a docs.config.js

Quick start

# In your project
npx supadocs init
npx supadocs dev

This creates:

docs/
  introduction.mdx
docs.config.js

Open http://localhost:3900.

Usage

1. Install

npm install supadocs

2. Create docs.config.js

export default {
  name: 'My Project',
  docsDir: 'docs',

  theme: {
    accent: '#6366F1',
  },

  landing: {
    headline: 'My Project Docs',
    description: 'Everything you need to get started.',
    primaryAction: { label: 'Get Started', href: '/introduction' },
    cards: [
      { title: 'Quick Start', description: 'Up and running in 5 minutes.', icon: 'rocket', href: '/quickstart' },
    ],
  },

  navigation: [
    { group: 'Getting Started', pages: ['introduction', 'quickstart'] },
  ],

  links: [
    { label: 'GitHub', href: 'https://github.com/you/repo', icon: 'github' },
  ],
};

3. Write MDX

---
title: Introduction
description: Welcome to the docs.
---

## Hello

<Note>
Built-in components are available in every MDX file. No imports needed.
</Note>

<CardGroup cols={2}>
  <Card title="Guide" icon="book-open" href="/guide">
    Step-by-step walkthrough.
  </Card>
  <Card title="API" icon="code" href="/api">
    Full API reference.
  </Card>
</CardGroup>

4. Run

npx supadocs dev     # dev server on :3900
npx supadocs build   # static site to dist-docs/

Components

All components are available in MDX without importing.

| Component | Usage | |-----------|-------| | <Note> | Info callout (blue) | | <Warning> | Warning callout (yellow) | | <Tip> | Tip callout (green) | | <Info> | Info callout (blue) | | <Card title="" icon="" href=""> | Feature card. icon is any Lucide icon name. | | <CardGroup cols={2}> | Grid of cards | | <CodeGroup> | Tabbed code blocks | | <Tabs> / <Tab label=""> | Generic tabs | | <Steps> / <Step title=""> | Step-by-step guide | | <Accordion title=""> | Collapsible section |

Config reference

export default {
  name: 'Project Name',
  logo: '/logo.svg',                        // or { light: '...', dark: '...' }
  favicon: '/favicon.png',
  docsDir: 'docs',                           // or '.' for root-level MDX
  port: 3900,
  outDir: 'dist-docs',

  theme: {
    accent: '#FF6C37',
    accentHover: '#E85A28',
    font: "'Inter', sans-serif",
    fontMono: "'JetBrains Mono', monospace",
    radius: '6px',
    colors: {                                // override any CSS variable
      bg: '#FAF8F6',
      bgCard: '#FFFFFF',
      bgSurface: '#F2EFEB',
      text: '#5C5650',
      textHeading: '#2D2A26',
      textMuted: '#9C958E',
      border: '#E8E4DE',
    },
    customCss: '',                           // raw CSS injected into <head>
  },

  landing: {
    headline: 'Project Docs',
    description: '...',
    primaryAction: { label: 'Get Started', href: '/intro' },
    secondaryAction: { label: 'GitHub', href: '...' },
    cards: [
      { title: '...', description: '...', icon: 'rocket', href: '/...' },
    ],
  },

  navigation: [
    { group: 'Section', pages: ['page-slug', 'folder/page'] },
  ],

  tabs: [
    { label: 'Docs', href: '/introduction' },
    { label: 'API', href: '/api/overview' },
  ],

  links: [
    { label: 'GitHub', href: '...', icon: 'github' },
  ],
};

Example

See the example/ directory for a complete working example.

cd example
npx supadocs dev

Documentation

Full documentation at docs.supaproxy.cloud.

Package exports

The ./components export points to raw TypeScript source (client/components/index.ts). This is intentional: supadocs is a Vite-based framework and is consumed by projects that run through Vite, which handles TypeScript natively. The source export works correctly in that context.

If you are importing supadocs components outside of a Vite pipeline, you will need to compile the TypeScript yourself.

License

MIT