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

create-zachflow

v1.7.0

Published

Bootstrap a new zachflow project (clone-and-strip).

Readme

create-zachflow

Bootstrap a new zachflow project. Zero runtime dependencies — uses only git and Node's built-in node:child_process/node:fs/node:path.

Usage

npx create-zachflow my-project

This:

  1. Shallow-clones the zachflow repo to my-project/ at the tag matching this package's version ([email protected]git clone --branch vX.Y.Z)
  2. Strips development artifacts (.git/, docs/superpowers/, etc.)
  3. Re-initializes git with a fresh first commit
  4. Auto-runs scripts/init-project.sh (the interactive wizard) when stdin is a TTY — one command, end-to-end setup.

In a non-TTY context (CI, redirected stdin) or with --no-init, the wizard is skipped and the manual next-step commands are printed instead.

Options

| Flag | Default | Description | |------|---------|-------------| | --repo=<url> | github.com/hx2ryu/zachflow.git | Repo URL | | --branch=<name> | (none) | Branch to clone (e.g. main) | | --tag=<tag> | v<pkg-version> | Tag to clone. Defaults to this package's version, so [email protected] clones zachflow at vX.Y.Z. | | --no-init | (off) | Skip auto-running the wizard. Use for CI or when you want to inspect the project before initializing. | | --help, -h | | Show help |

Env vars: ZACHFLOW_REPO_URL, ZACHFLOW_REF (overrides the default ref).

What gets stripped

The following are removed from the cloned repo:

  • .git/ (replaced with fresh git init)
  • docs/superpowers/ (zachflow design history — for contributors)
  • .zachflow/ (per-project state — wizard creates fresh)
  • node_modules/, dist/, package-lock.json (regenerated)

What stays: workflows/, plugins/, scripts/, templates/, .claude/, schemas/, tests/, packages/, all root docs (README, MANUAL, ARCHITECTURE, CONTRIBUTING, CHANGELOG, LICENSE).

Alternative install paths

If you can't use npm directly:

  • GitHub Release tarball (legacy bootstrap path, still maintained):
    npx https://github.com/hx2ryu/zachflow/releases/download/vX.Y.Z/create-zachflow-X.Y.Z.tgz my-project --tag=vX.Y.Z
  • Repo clone:
    git clone --depth 1 --branch vX.Y.Z https://github.com/hx2ryu/zachflow.git zachflow-template
    node zachflow-template/packages/create-zachflow/index.js my-project --tag=vX.Y.Z

License

MIT