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

@rb-mwindh/next-version

v1.0.3

Published

CLI to discover the next version of a package based on the commit history and the conventional commit specification.

Readme

next-version

npm version

A CLI and GitHub Action to compute the next semantic version for your npm package using Conventional Commits, git tags, and the npm registry. Inspired by semantic-release, but focused on CI/CD and monorepo-friendly workflows.


Features

  • Computes next version based on commit history and tags
  • Supports prerelease channels (e.g. develop, beta) with semantic-release-like counters
  • Integrates with npm registry to avoid version collisions
  • Usable as a CLI or as a GitHub Action
  • Customizable branch/channel rules

Usage

CLI

Install globally or use via npx:

npx @rb-mwindh/next-version --package <name> --branch main

Options

  • --package <name>: npm package name (required)
  • --cwd <path>: working directory (default: current)
  • --tag-prefix <prefix>: git tag prefix (default: "v")
  • --current-branch <name>: branch name (default: GITHUB_REF_NAME)
  • --branches <json>: branches config as JSON array (semantic-release format)
  • --branch <name>: simple branch entry (repeatable)
  • --reachable-tags-only: only tags reachable from HEAD (default)
  • --all-tags: consider all tags in repo
  • --fail-if-no-bump: exit non-zero if no bump is recommended
  • --json: print result as JSON

Examples

# Compute next version for main branch
npx @rb-mwindh/next-version --package @scope/corelib --branch main

# Use custom branches config (semantic-release style)
npx @rb-mwindh/next-version --package mylib --branches '[{"name":"main"},{"name":"develop","prerelease":"dev"}]'

# Output as JSON
npx @rb-mwindh/next-version --package mylib --branch main --json

GitHub Action

Add to your workflow:

- uses: rb-mwindh/next-version@main
  with:
    package: '@scope/corelib'
    branch: main
    tag-prefix: 'v'
    cwd: ${{ github.workspace }}

Action Inputs

  • package: npm package name (required)
  • branches: branches config as JSON array (semantic-release format)
  • branch: simple branch entry (repeatable)
  • tag-prefix: git tag prefix (default: "v")
  • cwd: working directory (default: GITHUB_WORKSPACE)
  • reachable-tags-only: only tags reachable from HEAD (default: true)
  • fail-if-no-bump: fail if no bump is recommended (default: false)

Action Outputs

  • version: computed next version
  • channel: release channel / npm dist-tag
  • bump: bump type (major, minor, patch, premajor, etc.)
  • already-published: whether this version is already published
  • last-stable-version: last stable version from tags
  • last-stable-tag: last stable git tag
  • next-base-version: next base version (X.Y.Z)
  • prerelease-id: prerelease identifier (if applicable)
  • prerelease-counter: prerelease counter (if applicable)
  • json: full result as JSON

Development

Build

This project uses @vercel/ncc to bundle all runtime dependencies for CLI and GitHub Action. The output is committed to bin/.

npm ci
npm run build
  • TypeScript builds to dist/
  • Bundles are created in bin/cli/ and bin/action/
  • Only bin/ is versioned (see .gitignore)

License

MIT © Markus Windhager