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

next-version

v0.11.7

Published

Imcrement version on multiple files

Readme

next-version

Change version numbers in multiple files using semver.

Checks the highest version number in the specified files and changes all to the highest number. It can bump major, minor or patch following semver. It can append a release and/or build suffix. Build number can also be extracted from the number of Git commits.

It can even bump itself!

Javascript

var version = require('next-version');
version(files,options,callback);

Options

options.major

Type: Boolean|Number Default value: false

options.minor

Type: Boolean|Number Default value: false

options.patch

Type: Boolean|Number Default value: true

options.version

Type: String

options.git

Type: Boolean Default value: false Appends a build number based on the number of GIT commits, ie: v1.2.3+897.

options.regex

Type: Regexp|Regexp[] Default value: /\d+\.\d+\.\d+/

examples

var version = require('next-version');
version(['foo.txt','bar.txt'],{minor:true},console.log.bind(console,'done');

CLI

Usage: next-version [options] <files ...>

Options:

-h, --help output usage information -m, --major [major] Bump or set major version -i, --minor [minor] Bump or set minor version -p, --patch [patch] Bump or set patch version -v, --version [version] Set the full version number -b, --build [build] The build number -g, --git Git revision number as build number -r, --regex [regex] Regex to find version number with

examples

next-version --major=3 foo.js bar.js

next-version --minor=3 foo.js bar.js

next-version --patch=3 foo.js bar.js

next-version --vs="2.3.4" foo.js bar.js