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

reference-docs

v1.4.0

Published

Invocation-only skills and scaffold for release-anchored reference documentation refreshed from tag diffs.

Readme

reference-docs

Invocation-only skills and a scaffold for release-anchored reference documentation.

Install

npx reference-docs init --project-name "My App"

The default root is reference/. Choose a case-preserving or nested relative root during initialization when the project requires it:

npx reference-docs init --project-name "My App" --reference-root Reference
npx reference-docs init --project-name "My App" --reference-root docs/reference

The configured root is stored in .reference-docs/install.json and is immutable after initialization. Absolute paths and . or .. segments are rejected.

The package works independently of any planning workflow. A tag diff is the source of truth; context/ and decisions/ are optional enrichment when they exist. Reference pages must remain understandable after disposable planning context and closed cycles are deleted.

Use

Create a baseline reference for this repo.
Refresh reference from <previous-tag> to <new-tag>.

Skills are invocation-only and never run automatically.

Project Extensions

Put durable local authoring rules in <reference-root>/_authoring/project.md. Package updates never overwrite this file, terminology, area guides, templates, release history, reference pages, or unknown files.

The package manages the two reference skills plus the generic authoring README and workflow. Marker-delimited sections in AGENTS.md and the skills README are also refreshed safely.

Safe Updates

npx reference-docs@latest update

Updates preflight every managed file. If a managed file was edited, deleted, or replaced with unmanaged content, the command writes nothing and lists all conflicts. Move project rules to the project overlay, then retry. --force replaces only conflicted package-managed files; it never removes whole directories or unknown project files.

Existing 1.x installations migrate automatically when their managed files are unchanged. Existing case variants such as Reference/ are inferred during the metadata upgrade. For a repository with no installation metadata, run init with its existing root; initialization merges missing files without replacing project content.

Commands/options: init, update, status, --target, --project-name, --reference-root, --dry-run, and --force.