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

@cssdoc/typedoc

v0.14.2

Published

A TypeDoc plugin that emits CSS reference pages (via @cssdoc/markdown) alongside a TS API-docs build and merges them into the TypeDoc sidebar.

Readme

@cssdoc/typedoc

A TypeDoc plugin that makes CSS docs ride along with a TS API-docs build. After TypeDoc renders, it emits CSS reference pages (via @cssdoc/markdown) into the output directory and merges them into typedoc-sidebar.json — so the CSS reference themes identically and sits in the same navigation.

Install

npm i -D @cssdoc/typedoc typedoc typedoc-plugin-markdown

Setup

// typedoc.json
{
  "plugin": ["typedoc-plugin-markdown", "typedoc-vitepress-theme", "@cssdoc/typedoc"],
  "cssdocCss": ["../packages/ui/dist/components.css"],
  "cssdocOut": "css",
  "cssdocLabel": "CSS",
  "cssdocBaseHref": "/api/css/",
}

| Option | Meaning | | ---------------- | -------------------------------------------------------------- | | cssdocCss | CSS source file paths whose doc comments become the reference. | | cssdocOut | Output subdirectory for the CSS pages (default css). | | cssdocLabel | Sidebar section label (default CSS). | | cssdocBaseHref | Link prefix for the pages/sidebar (default <cssdocOut>/). |

Programmatic use

For finer control (e.g. injecting a token resolveToken hook), call emitCssApi directly from your own build script:

import { emitCssApi } from "@cssdoc/typedoc";

emitCssApi({
  outputDirectory: "docs/api",
  css: ["dist/components.css"],
  baseHref: "/api/css/",
  resolveToken: (name) => myTokenIndex.get(name),
});

The @demo block-tag rewriter is a separate, generic TypeDoc plugin — it has nothing to do with CSS and is not part of this package.

License

MIT