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

ez-release

v0.1.3

Published

Release npm packages easily

Downloads

9

Readme

ez-release

Release npm packages easily.

ez-release is a command that combines common tasks about package publishments.

  1. Generate changelog via git changelog command from git-extras.
  2. Update the version field in package.json.
  3. Commit these two files.
  4. Tag current version.
  5. Push commit and tag onto remote.
  6. Publish the package.

Here's the list of commands that will be executed.

$ ez-release patch --dryrun
     $ npm version patch --no-git-tag-version
     $ git changelog --tag 0.1.2
     $ git add package.json
     $ git commit -m 0.1.2
     $ git tag v0.1.2
     $ git push origin
     $ git push origin --tags
     $ npm publish

Running all the steps listed above manually can be tiresome and error prone. So ez-release come to rescue. All you have to do is specify the new version, whether it's a major, minor, or patch version bump. Then edit the generated changelog. You are good to go.

Install

$ brew install git-extras       # tested with version 3.0.0
$ npm install ez-release -g

Usage

$ ez-release patch -m 'Upgrade to %s for reasons'
$ ez-release patch --dryrun             # see what commands will be executed
$ ez-release --help
Usage ez-release [<newversion> | patch | minor | major | prepatch | preminor | premajor | prerelease]


  Options:

    --message, -m   The message for the commit of version and changelog. If the
                    message contains %s then that will be replaced with the
                    resulting version number.

    --dryrun, -d    Test run.

Specify npm

$ NPM=cnpm ez-release