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 🙏

© 2024 – Pkg Stats / Ryan Hefner

nver

v0.0.15

Published

Fast and easy-to-use semantic versioning (semver) tool for node packages

Downloads

11

Readme

# nver Build Status

Command-line version control tool (semver) for node packages

Example Usage:

Increment patch version (default):

To increment the patch level of your node package, simly enter nver:

nver
> Patch version incremented to 0.0.2 (was 0.0.1)

Or nver --patch:

nver --patch
> Patch version incremented to 0.0.3 (was 0.0.2)

Or, if you want to be SUPER explicit, enter nver up --patch:

nver up --patch
> Patch version incremented to 0.0.3 (was 0.0.2)

When calling the nver command, it will assume you want to go up, and assume you want to go up at the patch-level, as this is the most common use case when changing semantic versions.

Increment minor or major version:

To increment a minor version, simply enter nver --minor:

nver --minor
> Minor version incremented to 0.1.3 (was 0.0.3)

And to increment a major version, enter nver --major:

nver --major
> Major version incremented to 1.1.3 (was 0.1.3)

Decrementing version:

It's easy to decrement versions too, should you need to.

To decrement the patch version of your node package, enter nver down:

nver down
> Patch version decremented to 1.1.2 (was 1.1.3)

If you want to decrement a non-patch version, simple pass the --major or --minor flag along with the down command:

nver down --major
> Major version decremented to 0.1.2 (was 1.1.2)

Display current version:

To find out what the current version of your node package is, enter nver current:

nver current
> 0.0.1

If the version is not yet set, you'll see an error message:

nver current
> Error: No version defined!

No need to panic; you can set the version using nver init:

nver init
> Package version initialized to 0.0.1