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

satoshibits-cli

v1.0.0

Published

[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg)](https://github.com/prettier/prettier) [![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg)](http://commitizen.github.io/cz-cli/) [!

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

satoshibitssatoshibits

Keywords

Readme

satoshibits-cli

code style: prettier Commitizen friendly license

This is a monorepo for managing and publishing CLI packages responsible for generating templates.

Getting started

You can find each CLI's instructions in their respective READMEs.

Working within the monorepo

Changes that should trigger a package publish

  1. Make your changes and group them to the relevant package.
  2. pnpm run commit:publish — this runs changeset, stages the changeset file, and opens commitizen.
  3. Open a PR to main. CI runs build, lint, typecheck, and tests automatically.
  4. On merge, the release workflow creates a "Version Packages" PR that bumps versions and updates changelogs.
  5. When the Version Packages PR is merged, changed packages are published to npm.

Changes that don't require publishing

  1. Make your changes.
  2. Run pnpm changeset --empty to create an empty changeset (signals "no release needed"). This is required because CI enforces changeset presence for any PR that touches package files.
  3. pnpm run commit:cz

If your changes are entirely outside of packages/ (e.g., CI config, root docs), you can skip the empty changeset.

Adding a new package

npm enforces 2FA on first-time package publishes, so new packages cannot be published from CI until they exist on the registry.

  1. Create your package under packages/.
  2. Publish the first version manually with 2FA from your local machine:
    cd packages/<new-package>
npm publish --access public
  3. Update your npm granular access token to include the new package.
  4. From this point on, CI handles all subsequent releases.

The ci:publish script includes a pre-publish check (scripts/check-new-packages.js) that will fail the release early with clear instructions if a package hasn't been manually published yet.

CI/CD

| Workflow | Trigger | What it does | |----------|---------|--------------| | CI (.github/workflows/ci.yml) | Pull request to main | Runs build, lint, typecheck, test, test:e2e, and validates changeset presence | | Release (.github/workflows/release.yml) | Push to main | Creates a Version Packages PR (via changesets), or publishes to npm if versions were already bumped |

Prerequisites

  • Set NPM_AUTH_TOKEN as a repository secret in GitHub. Generate one here.
  • The token must be a granular access token with publish permissions for all @satoshibits/* packages.