Share your code. npm Orgs help your team discover, share, and reuse code. Create a free org »


    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:

    > 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


    npm i nver

    Downloadslast 7 days







    last publish


    • avatar