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

@itsmworkbench/cli

v0.3.12

Published

How to do a cli

Readme

Overview

This is about the tenth time I have cut and pasted the same thing.

It's time to make a module that can do this for me!

Config file

Most CLIs have some config. Not all but some. This might be

  • Stored in '~/.xxx.json'
  • Stored in the current directory
  • Stored in a parent directory
  • Stored in a directory xx hanging off a parent directory
  • etc... So many options so we abstract it

Observations

  • We need the config before we build the cli because often we use it in the construction of the cli.
  • Often the config needs validating and errors reporting.
  • We will probably need commands to look at the config and validate it for every CLI we build.
  • We need to build the config... we might add things that aren't serializable to it: this is our dependency injection too

Building the CLI

  • We always need --version. It's hard to do that here so pass it in...
  • We need the config before we build the cli
  • We need to be able to add config commands to the cli (but not do it automatically)

finding your version

In your main file. Because of the use of require it's hard to do this in a library.

export function findVersion () {
  let packageJsonFileName = "../package.json";
  try {
    return require ( packageJsonFileName ).version
  } catch ( e ) {
    return "version not known"
  }
}