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

devup

v0.3.1

Published

git utility to version and tag

Readme

devup

Bump all the .versions in all your .jsons and make a tag with a message

npm install devup -g

Run with:

$ devup

must be run in the top level of your project (or with all of your versioned .json files. all .json files must be in the same directory)

you may cancel at the time of tag message request with no fear. all changes stay local until you choose to push them.

Options:

-h, --help  Show help                                                [boolean]

Examples:

Bump patch version number (major.minor.patch)

$ devup

Bump minor version number (major.minor.patch)

$ devup -t minor

Bump major version number (major.minor.patch)

$ devup -t major

todo:

  • escape messages so that special characters can be used
  • catch things after the version numbers have been updated so that they can be rolled back if the deal fails
  • error out if no files with version numbers are found on validation