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

whatbump

v2.1.0

Published

Get a recommended version bump based on conventional commits

Downloads

6

Readme

whatbump

Extremely basic utility to find out what semantic version bump should occur for a given folder based upon conventional commit messages. Outputs major, minor, patch or an empty string based upon what semantic release the commits describe.

Installation:

npm install -g whatbump

Usage:

whatbump [options] [path]

Options:

| Options | Descrioption | Default | | --- | --- | --- | | --base | Git ref or sha to compare against when viewing differences.| main | | --ref | Git ref of sha to use as the current state. | HEAD | | --preset | Changelog processor to use for determining bump method. |conventionalcommits | | --type-filter | Comma separated list of commit types to accept, ignoring all other types. | fix, feat, feature, breaking | | --changelog | Output changelog body| | | --json | Output both bump level and changelog as a JSON object| | | --version | Starting semver version number. If not provided, whatbump will look for a package.json in the target directory. | | | --repo | Repo url for creating links in the changelog. If not provided, whatbump will look for it in a package.json in the target directory. | | | --name | Package name used to prefix the version in the changelog. If not provided, whatbump will look for it in a package.json in the target directory. | |

API

Note: Invoking the api directly requires supplying all of the below config options. There are no defaults, like above.

import whatbump from 'whatbump';

const {
  level, // bumping level (major, minor, patch)
  version, // new version number
  commits, // array of parsed commits that were found
  changelog, // generated changelog result
} = await whatbump({
  cwd,  // directory to read commits from
  base, // Git ref or sha to compare against when viewing differences.
  ref,  // Git ref of sha to use as the current state
  preset, // Commit analysis preset
  types, // Array of the commit types that should be analyized
  context: {
    version, // current starting semver version
    name, // package name that will prefix the version number in changelogs
    repoUrl  // repo url (for generating changelog links)
  }
});