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

ragharwal

v2.0.0

Published

A Personal npx Card

Readme

NPX Card

Type npx ragharwal to connect with me directly via console or terminal

Steps to Create your Own NPX Card

npm init

Start a new node project and name it whatever you want. You could choose to name it after the executable you want to expose. It's not necessary but conventions are nice, and it makes your binary more npx friendly.

mkdir ragharwal
cd ragharwal
npm init -y

At first, let's get the necessary CLI working.

echo >> index.js

Now open the new file in your favorite editor. I've have been using VS Code.

console.log('Working')

Be creative and add logic to create your own index.js or you can simply copy my index.js file and necessary changes as required.

Ship It

That's an entirely functional first release! You just need to modify your package.json to let npm know to link your executable and you are off.

{
    // ...
    "bin": "./index.js",
    // ...
}

By defalut, npm will expose your binary using the same name as your package.

Share your new CLI with the World!

Now anyone can leverage your new CLI using npx, without needing to install it locally.

npx $YOUR_PACKAGE_NAME