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

@svartz/theme-docs

v2.3.0

Published

A Svartz theme for package reference docs: modules, classes, interfaces, functions, and types.

Readme

@svartz/theme-docs

Reference docs for a package: guides, then every exported class, interface, function, type, and constant, one note per symbol. The structure follows TypeDoc, rustdoc, and Starlight; the look is Svartz's.

// svartz.config.ts
vaults: [{
  id: "docs",
  path: "docs",
  target: { type: "static" },
  theme: {
    base: "@svartz/theme-docs",
    version: "1.0.0",
    routes: { folders: "api" },
    nav: { GitHub: "https://github.com/you/package" },
  },
}],

What it renders

| Page | Contents | | --- | --- | | Symbol | Kind badge, name, since, summary, the note's own Markdown, signature (tabs for overloads), deprecation, type parameters, parameters, returns, throws, hierarchy, members by kind, "Defined in" | | Guide | Any note without a symbol: plain prose | | Home | The home note, then one card per module | | Module | /folders/:module/ (or your routes.folders): symbols grouped by kind with summaries | | Reference | /folders/: every symbol by kind | | Recently updated | /feed/ |

The theme extends @svartz/theme-minimal: it swaps the frame, top bar, page head, right column, and footer, and adds a symbol page renderer. Minimal's explorer, search, drawer, and previous/next links come with it. In the explorer, each symbol shows its kind badge and name, listed by kind before the folder's guides. "On this page" includes the generated sections.

Frontmatter

description: Wrap a theme manifest so Svartz validates it.   # the summary
symbol:
  kind: function        # namespace, class, interface, type, enum, function, variable
  name: defineTheme
  signatures:           # or `signature` for one
    - "defineTheme(theme: SvartzTheme): () => SvartzTheme"
  typeParameters: [{ name: T, constraint: Record<string, unknown> }]
  parameters:
    - { name: factory, type: "(options?: T) => [[SvartzTheme]]", optional: false, description: … }
  returns: { type: "[[SvartzTheme]]", description: … }
  throws: [{ type: ThemeValidationError, description: … }]
  extends: ["[[Base]]"]
  implements: []
  members:              # for classes and interfaces
    - { name: load, kind: method, signature: "load(): Promise<void>", description: …, static: false }
  source: https://github.com/…/define-theme.ts
  since: 1.0.0
  deprecated: Use `[[VaultView]]`.

[[Name]] in types and descriptions links to that symbol's note; backticks render as code. The schema is exported as DocSymbol. A TypeDoc plugin should emit exactly this shape.

Develop

pnpm svartz dev --vault showcase-docs