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

@zumerbox/bump

v1.3.0

Published

Interactive semver bump driven by [Conventional Commits](https://www.conventionalcommits.org/). Reads commits since the last tag, classifies them, suggests `major` / `minor` / `patch`, and runs `npm version` for you. Supports prereleases and a non-interac

Readme

@zumerbox/bump

Interactive semver bump driven by Conventional Commits. Reads commits since the last tag, classifies them, suggests major / minor / patch, and runs npm version for you. Supports prereleases and a non-interactive mode for CI.

Install

npm install @zumerbox/bump --save-dev

Usage

Interactive (default)

npx @zumerbox/bump

The tool will:

  1. Refuse to run if the working tree is dirty.
  2. List the commits since the last tag, grouped by conventional type:
    • 🔥 BREAKING CHANGE — feat!:, fix(scope)!:, or any commit with BREAKING CHANGE in the body.
    • feat: — minor bump.
    • 🛠 fix: — patch bump.
    • 📦 chore: / docs: / refactor: / perf: / ci: / test: / build: / style: / revert: — informational only.
    • ❓ commits without a conventional prefix.
  3. Suggest the next version. Press Enter to accept or type your own.
  4. Ask if it should be a prerelease, and if so the tag (default beta) — auto-numbers -beta.0, -beta.1, etc.
  5. Run npm version <new>, which creates the commit and tag.

Non-interactive (CI)

bump --patch                        # bump 1.2.3 → 1.2.4
bump --minor                        # bump 1.2.3 → 1.3.0
bump --major                        # bump 1.2.3 → 2.0.0
bump --major --prerelease=rc        # 1.2.3 → 2.0.0-rc.0 (auto-increments)
bump --prerelease                   # use the suggested bump, tag as -beta.N
bump --dry-run --patch              # prints the npm version command, runs nothing

--dry-run (-d) prints npm version … instead of running it. Useful in --patch/--minor/--major mode to preview the bump.

Help

bump --help

Conventional commit detection

A commit subject is classified as breaking when it matches:

  • ^<type>(\(scope\))?!: (e.g. feat!:, fix(api)!:)
  • or contains the literal phrase BREAKING CHANGE

The earlier 1.x versions used a looser pattern that flagged any line containing !, producing false positives on subjects like fix: handle ! in regex. 2.x is strict.

Pairing with @zumerbox/changelog

A typical release script in your package.json:

{
  "scripts": {
    "bump": "npx @zumerbox/bump",
    "postversion": "npx @zumerbox/changelog && git add CHANGELOG.md && git commit -m \"Update changelog\" && git push --follow-tags"
  }
}

npm run bump triggers npm version internally, which runs postversion after creating the version commit and tag.

License

MIT