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

npm-increase-version

v2.2.4

Published

release npm packages without hassle

Downloads

3

Readme

npm-increase-version

Increments the major/minor/fix version of your package.json for you!

Current working conditions

Install: npm install --save-dev npm-increase-version

Add in package.json:

  ...
  "scripts": {
    ...
    "increase-version": "node_modules/npm-increase-version/index.js"
  },

Run with: npm run increase-version -- -i [f/m/M]

Enjoy :)

Install

Run npm install -g npm-increase-version

Usage

  Usage: npm-increase-version [options] [command]
  
  Commands:
    help     Display help
    version  Display version
  
  Options:
    -c, --ci                Use in CI environment. If true, determines the version solely from the last commit message (release:[fix|minor|major]). Example: release:fix fix the broken thing. (disabled by default)
    -h, --help              Output usage information
    -i, --increase [value]  The type of version to increment. For example, M or major increments the major version, m the minor, and f the fix (defaults to "minor")
    -t, --tag               Returns the tag to create (disabled by default)
    -v, --version           Output the version number

Example:

cd my-package # current version: 2.4.19
npm-increase-version -i fix
# output --> Upgraded from version 2.4.19 to version 2.4.20.
# current version 2.4.20
npm-increase-version
# output --> Upgraded from version 2.4.20 to version 2.5.0.
# current version 2.5.0
npm-increase-version -t
# output --> v2.5.0
npm-increase-version -i M
# output --> Upgraded from version 2.5.0 to version 3.0.0.
# current version 3.0.0

Usage with CI

First, integrate into your CI pipeline after the tests:

- npm install -g npm-increase-version
- npm-increase-version --ci

To work, your commits must be the following:

  • For a major release: release:major <your commit message>
  • For a minor release: release:minor <your commit message> or release: <your commit message>
  • For a fix: release:fix <your commit message>

If you just want to commit without releasing, just commit as you would normally; as long as your commit message does not start with release: it will be fine.