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

git-flow-bump-type

v1.0.4

Published

Determine the bump type based on git flow

Readme

#Git Flow Bump Type

This determines the semver bump type (major, minor, patch) of your git project according to an opinionated git workflow.

Set up your major, and minor branch names in the options, from which merges will trigger according versions and all other branch merges will be considered patch.

Never concern yourself with what kind of bumping to give your next version again. Let your workflow do the talking.

Getting Started

npm install --save git-flow-bump-type

Use it from Node.js

var gitFlowBumpType = require('git-flow-bump-type');
gitFlowBumpType({/* options */})
.then(function (bumpTo) {
  console.log('Bump to: ' bumpTo);
  // Would log 'major', 'minor', or 'patch'
});

Options

Defaults

gitFlowBumpType({
  masterOnly: true,
  majorBranch: 'remotes/origin/release',
  minorBranch: 'remotes/origin/develop'
});

options.masterOnly - Boolean

Fail to determine a bump type if you aren't currently checked out on master If you determine versions from a branch other than master, make this false

options.majorBranch

The branch that should contain the current commit if a Major bump

options.minorBranch

The branch that should contain the current commit if a Major bump

How it is intended to work

There are a few assumptions being made when using this module:

  1. The commit you are determining a bump for has been merged to master and pushed to origin
  2. You are trying to use automation, such as a continuous delivery server, to bump for you. Where only an individual commit is being examined and not all the code can be expected to be local.

If that's not the case and you want to determine bumps from your local repository, simply override the defaults to

{
  majorBranch: 'release', //or whatever you call it
  minorBranch: 'develop'
}