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

@basemachina/minidoc

v0.1.1

Published

A minimal MDX documentation generator with built-in diagrams, preview, static hosting, CLI, and agent skill support.

Readme

minidoc

Minimal MDX documentation with built-in diagrams, static output, a preview app, a CLI, and installable agent skills.

npx @basemachina/minidoc init minidocs
npx @basemachina/minidoc dev minidocs
npx @basemachina/minidoc build minidocs
npx @basemachina/minidoc skill install --agent codex --scope global
npx @basemachina/minidoc skill install --agent claude --scope project

Docs source lives in minidocs/. Static output is written to minidocs/out/.

Publishing

The package is scoped and public. Releases are managed with Changesets:

Prepare release

pnpm changeset

Release flow

  1. Create feature PRs against develop.

  2. For every non-release PR, add a changeset:

    pnpm changeset

    Choose patch, minor, or major, then write the user-facing release note.

  3. If a PR should not publish a new package version, add an empty changeset:

    pnpm changeset --empty

    Empty changesets are still consumed by the Version Packages PR, so non-release changes can move from develop to main without bumping npm.

  4. Merge approved feature PRs into develop.

  5. Open the Prepare release button above, choose Run workflow, and leave source_branch as develop unless you are preparing from a temporary branch. The workflow reads pending changesets, updates versions and changelogs, and opens or updates the Version Packages PR into main.

  6. Review and merge the Version Packages PR into main. The publish npm package workflow publishes the new npm version, updates the npm latest dist-tag, pushes the matching vX.Y.Z Git tag, and creates the GitHub Release.

The changeset check workflow fails PRs to develop that change the package without a changeset. main should only receive Version Packages release PRs. The repository secret NPM_TOKEN must have publish access to the @basemachina npm scope.