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

auto-bump

v0.0.10

Published

Bump version in package.json automatically according to git log

Downloads

10

Readme

Choose Language: English | 简体中文

Background

Help to bump version in pacakge.json according to commit types (such as fix, feature or breaking change).

For example: If previous version is "1.0.0" (using git tag), and there are 3 commits after that version, they are:

  • BREAKING CHANGE(button): add button api
  • feat(button): add button
  • fix(button): fix button bug

The version should be 2.1.1.

By inputting yarn auto-bump, version in package.json will be updated to 2.1.1.

Install

Preconditions

  • There is only one root branch in git history.
  • Subjects of commits should align to Conventional Commits (or you need to add autoBump config in package.json to specify custom matching patterns).
$ yarn add -D auto-bump

or

$ npm install -D auto-bump

Usage

Only one command to bump your version:

$ yarn auto-bump

At first auto-bump will check if there is tag for previous version. Or it will traverse from the first commit of root branch and bump version for each commit. And you will see package.json version is udpated.

Please notice that auto-bump will check commit subject to decide bumping major/minor/patch version. So by default your commit subject should follow Conventional Commits. Or your can add custom matching patterns in package.json, you can refer package.json in this repository as example.

Contribute

WIP.

TODO

  • Add API for Javascript
  • Add life cycle functions

License

MIT © Hexxa