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

conventional-release

v1.0.2

Published

Module to complete release process

Downloads

3

Readme

Automatically release your npm module

This command line script allows you to automatically release your npm module from the git repository. It assumes you follow these rules:

  • You have initial tag on master branch matching your initial version of the version in package.json
  • You use Angular commit message convention
  • You only release on master branch

To make a release you need to commit (or merge from other branches) something on top of your initial tag. You SHOULD NOT modify your version in package.json manually. Then you can simply do clean clone from your origin and on master branch call:

$ conventional-release

The tool will automatically calculate new version number of your module (using mversion and conventional-recommended-bump, generate new CHANGELOG.md file (using conventional-changelog, update version in your package.json (and bower.json, if you have one) file, commit all changes to the repository and tag the new commit. At the end the tool will prompt you wether or not you want to push your changes to remote origin and automatically publish your new version to your default NPM registry.