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

runtests

v0.1.7

Published

A test runner/harness for use with TAP producing unit tests

Readme

Runtests

A simple test runner/reporter for use with TAP producing unit tests. I recommend building those tests with tape, but any TAP-producing harness will work.

Usage

runtests [options] [files]

By default, runtests will execute javascript files in the tests/ directory, i.e. tests/*.js. Test file 
names can be globbed. Javascript files will be run with Node.js. All other file types should have a shebang. 
Otherwise, runtests doesn't discriminate as to how the TAP output is produced, as long as it comes via STDOUT.

Options:

-q,  --quiet        Only print summary results
-s,  --shuffle      Run tests in a random order
-r,  --reverse      Run tests in reverse order
-v,  --verbose      Print more
     --beep         Audible beep at end if any tests failed
     --archive      Saves TAP outputs to a directory or archive (.zip, .tar, or .tar.gz)
-h,  --help         Display this help

If your project has a package.json file, it is common to specify a test command for npm, e.g.:

{
    ...
    "devDependencies": {
        ...
        "runtests": "~0.1.0"
    },
    "scripts": {
        "test": "runtests"
    }
}