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

rapid-release

v1.0.13

Published

Helps automate the required steps to create a new release

Readme

Rapid Release

Rapid Release is a tool to help automate the required steps to create a new release of your app.

Usage

npx rapid-release VERSION

VERSION can be any of major, minor, patch, premajor, preminor, prepatch, prerelease, 1.2.3 (uses npm version)

It makes a few assumptions about the project, so be sure those things are true with your project.

The main goal is to marge the develop branch into master, push everything and add the required tags. The main assumption is that you follow gitflow and you have a develop (or any branch name that contains the string dev) that you want to merge into master and release.

It also assumes that you want master and develop branch to have the exact same commits after the release is done, which is a good practise.

Actions

Following are the actions that Rapid Release executes, in the order those are executed.

  • Check if the current branch has the string dev in it's name
  • npm test run tests or skip them using flag -s
  • git pull make sure we have all changes
  • npm version VERSION VERSION is the version you specified
  • git push push the new commit that npm created
  • git push --follow-tags push the tag that npm created
  • git checkout master go to master branch
  • git pull make sure we have latest code
  • git merge DEV_BRANCH merge the branch we started in, to master
  • git push push the new release code
  • npm publish only if you used the -p flag
  • git checkout DEV_BRANCH go back to the branch we started at

Available flags

-s or --skip-tests to skip running the tests (npm test)
-p or --npm-publish to publish on npm (npm publish)