npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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




tag, push, and publish to npm and bower





Build, tag, push, and publish your repositories with one command.

Based on the lovely minus the changelog generation. I prefer managing the changelog manually, plus it's very easy to make that an additional step on per project.


$ npm install --save kn-release


Add it to your package.json scripts:

"scripts": {
  "release": "release --build"

And now run

$ npm run release

to release new versions of your package.

Build step

Pass --build flag to release to run npm run build after versioning, but before commiting, pushing and publishing. In this case, the build directory gets published to npm, not the root, so make sure to copy package.json and to your build dir in this case.

Here's an example I use for some of my projects:

rm -rf build

# npm CJS
babel -d build/lib ./lib
cp index.js package.json build

# standalone UMD
webpack index.js build/standalone.js

# print out the size info
echo "\nnpm build including deps is\n `bro-size build`"
echo "\nnpm build excluding deps is\n `bro-size build -u react`"

What it does

  1. prompts you for the new version
  2. runs tests
  3. updates package.json
  4. optionally runs npm run build and publishes the build dir instead of the root
  5. commits the version updates with a simple commit message ("Release {version}")
  6. creates the tag "v{version}"
  7. pushes master and the new tag to origin
  8. publishes to npm

But I have another step before I can tag and publish!

That's fine, just do your build first w/o committing, then run release. It'll all go in the same commit.