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

@alexraycan/bump-version-cli

v1.0.3

Published

A command-line utility for bumping the version of any project

Readme

bump-version-cli

A simple interactive CLI tool for bumping the version in your project's package.json and creating Git tags, with optional pushing to a remote repository.

Features

  • Interactive prompts for version bumping or tag creation
  • Supports all standard semver version increments (patch, minor, major, prepatch, preminor, premajor, prerelease)
  • Pre-release identifiers: standard, alpha, beta, rc
  • Creates annotated Git tags
  • Optionally pushes tags and commits to remote
  • Safe: checks for existing tags locally and remotely, with overwrite/force options

Installation

Clone this repository and install dependencies:

git clone <your-repo-url>
cd bump-version-cli
npm install

You can link the CLI for global use:

npm link

Usage

Navigate to your project directory (must contain a package.json), then run:

bump-version-cli

Or, if not linked globally:

npx path/to/bump-version-cli/index.js

How It Works

  1. Choose Action

    • Bump version (current: X.Y.Z): Increment the version in package.json and create a Git tag.
    • Create tag with current version (X.Y.Z): Only create a Git tag for the current version.
  2. Select Version Type
    If you choose to bump the version, select the type of increment:

    • patch, minor, major
    • prepatch, preminor, premajor, prerelease (with pre-release identifier: standard, alpha, beta, rc)
  3. Tag Handling

    • If a tag already exists, you can choose to overwrite it.
    • If pushing to remote, you can force-update the tag if it exists remotely.
  4. Push to Remote

    • Optionally push the commit and tag to your remote repository.

Example Session

? What do you want to do? (Use arrow keys)
❯ Bump version (current: 1.2.3)
  Create tag with current version (1.2.3)

? Select version bump type: (Use arrow keys)
❯ patch (1.2.3 → 1.2.4)
  minor (1.2.3 → 1.3.0)
  major (1.2.3 → 2.0.0)
  --- Pre-release ---
  prepatch (1.2.3 → 1.2.4-0)
  preminor (1.2.3 → 1.3.0-0)
  premajor (1.2.3 → 2.0.0-0)
  prerelease (1.2.3 → 1.2.4-0)

? Select pre-release (1.2.3 → …): (Use arrow keys)
❯ standard (1.2.3 → 1.2.4-0)
  alpha (1.2.3 → 1.2.4-alpha.0)
  beta (1.2.3 → 1.2.4-beta.0)
  rc (1.2.3 → 1.2.4-rc.0)

🚀 Running: npm version patch …
✅ Version changed: 1.2.3 → 1.2.4

? Push changes and tags to remote? (y/N)

Requirements

  • Node.js v14 or newer
  • Git installed and initialized in your project

Notes

  • The tool must be run from the root of your Node.js project (where package.json is located).
  • Make sure you have committed all changes before running the tool to avoid conflicts.

License

MIT