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

v0.4.1

Published

DocPensieve command-line interface (init, build, check, dev, serve)

Readme

docpensieve

Command-line interface

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.

Getting started

Nothing to install first: npx fetches the package.

npx docpensieve init my-site  # asks a few questions, then sets up the project
cd my-site
npx docpensieve dev           # builds, serves, watches and reloads

Installing it in a project

To pin the version a project uses — what continuous integration needs:

npm init -y                   # only when the folder has no package.json yet
npm install docpensieve
npx docpensieve init .

npm install only installs: it creates no site and asks nothing — init does. And npm installs in the nearest folder that has a package.json, going up from the current one: in a folder without one, the package lands in a parent folder and nothing appears where you are. Hence npm init -y first.

Commands

npx docpensieve init [dir]    # sets up a project and picks the theme
npx docpensieve dev           # builds, serves, watches and reloads
npx docpensieve build [ver]   # builds every version, or a single one
npx docpensieve check         # reads the produced site back: links, markup
npx docpensieve serve         # serves the output folder

init asks for the project name, its URL and the CSS framework, and installs DocPensieve's documentation in a section of the new site's menu, matching the installed version — --minimal leaves it out. The configuration file it writes lists every option, each with a comment. In a script or in CI, --yes --theme tailwind skips the dialogue.

The development server reloads the browser after every rebuild, through a script injected at serving time: the output of build stays free of JavaScript.

Updating

npm install docpensieve@latest

Run through npx alone, it needs nothing: npx docpensieve fetches the latest version by itself. A project set up with 0.1.0 can rename docpensieve.config.js to docpensieve.config.mjs, which Node reads as a module whatever the package.json says: the warning printed on every build goes away.

Documentation

See the repository.

License

MIT