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

cb-system

v2.0.0

Published

the system() you've been missing

Readme

cb-system

the system() you've actually missed

Installation

npm install cb-system

API

system(command)

system(command, args)

system(command, opts)

system(command, args, opts)

Uses child_process.spawn to spawn the process, and waits for it to exit. If everything goes okay, callback is called with no arguments. If the process exits abnormally, the callback is called with an error.

For clarity, command is allowed to be an array, for cases like vmadm boot, where vmadm clearly isn't a very useful description of what command is being run. This only makes a difference for error reporting.

ExitError

  • name: ExitError
  • stderr: stderr output of the process (Buffer)

then, depending on how it exited:

  • signal: signal that killed the process (string)
  • message: '`' + command + '` killed by signal `' + err.signal + '`: ' + err.stderr

or

  • code: exit code (integer)
  • message: '`' command + '` exited with ' + err.code + ': ' + err.stderr

Acknowledgements

This is literally a fork of then-system reworked to use callbacks. Whole refactor wound up being about 6 lines shorter.

Another fun fact: the total size of this module (including dependencies) with promises was 4084 lines of code, and is now reduced to 3213 lines of code.