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

hbobenicio-npm-publishing-example

v0.0.4

Published

Example project on how to publish an npm package to npm registry

Readme

hbobenicio-npm-publishing-example

Keep things out of your package

  • Run npm pack to check which files will be included

Use npm link to test your package

  • Inside another testing package, use npm link foo to link to the foo package. This will create a symlink, so you will not need to repack and readd that in order to test it. It's a way of live testing your package.

Publish it!

  • npm publish. Done.

What if your want to update it?

  • npm version VERSION will modify package.json version and commit the changes with git
  • npm version patch will do the same as above, but calculate the patching version of it
  • Republish it with npm publish

Useful Links

  • https://docs.npmjs.com/cli/link
  • https://docs.npmjs.com/misc/developers