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

@docpensieve/theme

v0.4.1

Published

DocPensieve theme system: composable providers (Tailwind, custom)

Readme

@docpensieve/theme

Composable themes

Part of DocPensieve, a static documentation site generator: Markdown and MDX in, static HTML out, one version per orphan branch, JSON-LD structured data from the frontmatter.

Installation

npm install @docpensieve/theme

Usage

Two themes ship — Tailwind and a dependency-free custom theme — behind the same contract. Templates ask the theme for their classes rather than hard-coding them, which gives two renderings for a single set of templates.

import { ThemeEngine, CustomProvider } from '@docpensieve/theme';

const engine = new ThemeEngine().register(
  'custom',
  new CustomProvider({ tokens: { '--dp-accent': '#008060' } }),
);

Writing your own takes two members:

import { BaseThemeProvider } from '@docpensieve/theme';
import type { ThemeOutput, CompileContext } from '@docpensieve/theme';

class MyProvider extends BaseThemeProvider {
  get classes() {
    return { nav: 'my-nav' };
  }
  async compile(context?: CompileContext): Promise<ThemeOutput> {
    return { css: '.my-nav{}', variables: {} };
  }
}

tailwindcss is installed with the package: the default theme needs it, and starting a project should not ask for anything more. The custom theme does not use it.

Documentation

See the repository.

License

MIT