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

@mmpg-soft/v-bump

v1.0.1

Published

A simple utility that bumps the version of your package according to the last commit message.

Downloads

11

Readme

V-Bump 🆙

V-Bump is a short utility that will help developer maintain clear versioning for their packages and projects. It works by parsing the git commit message and extracting the command and size of the commit or via command line arguments.

Getting started

Install the package with npm by running: npm install @mmpg-soft/v-bump.

How to use it

Triggering v-bump works by running v-bump in your terminal. The v-bump command takes several arguments that you can check by running v-bump -h. v-bump will by default, if no arguments are passed, try to read your latest git commit message versioning insructions. The script looks for something formatted like this: [[instruction:increment]]. A few use case would be:

  • [[patch:1]]: would turn 1.0.0 into 1.0.1
  • [[patch:2]]: would turn 1.0.1 into 1.0.3
  • [[minor:1]]: would turn 1.4.9 into 1.5.0
  • [[major:1]]: would turn 1.2.5 into 2.0.0

If you do not wish to run v-bump with automated git message instructions, you could pass some arguments as well. For most use cases, one argument is sufficient: -s (severity). Severity takes three values:

  • 'patch'
  • 'minor'
  • 'major'

Each of those will increment the relevant number by 1 if no value is specified. The value position are described as follows: major.minor.patch (ex: 1.0.2).

If you wish to increment the severity value by more than the default 1, you could pass -i (increment) followed by the value you wish to increment. Realistic examples would be:

  • v-bump -s patch -i 1: would turn 1.0.0 into 1.0.1
  • v-bump -s patch -i 2: would turn 1.0.1 into 1.0.3
  • v-bump -s minor -i 1: would turn 1.4.9 into 1.5.0
  • v-bump -s major: would turn 1.2.5 into 2.0.0
  • v-bump -s major -i 2: would turn 1.2.5 into 3.0.0