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

@roberp05/package-publishing

v4.0.0

Published

This is a test repo for npm publish and github tagging leading to `gh release`.

Readme

package-publishing

This is a test repo for npm publish and github tagging leading to gh release.

Versioning

major.minor.patch methodology, this is not breaking any ground in it implementation. Using npm version patch, npm version minor and npm version major. This process will incrememnt the version number automatucally.

npm publish

The npm cli contains all the necessary methods to do this process manually using npm publish --access public this does have the public access switch applied to it for this demo, this will not be necessary for the actual implementation.

git tag

Standard tagging in git is enough for us to be able to distinguish different tagged versions and download then, git tag -a "v1.0.4" -m "A message." then a tag push using git push origin v1.0.4.

github release

This will take tagging one step further, this will have a npmesque release page and downloading correctly with npm install this method also allows for the latest tag. This method will allow us to distinguish pre-release, release-candidate and alpha versionsof the same code and we can handle the scenarios separately.