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

taper

v0.5.0

Published

Taper (a fork of tapr) is a tap test runner that shows an appropriate level of detail with colorized output.

Readme

taper Build status npm package

Taper (a fork of tapr) is a Node.js tap test runner which allows stdout and stderr mixed in with the tap output. Also taper adds color to the output. Core based on Isaac Z Schlueter original tap runner.

For a nice description of Node.js Tap tests, see Isaac's readme on the node-tap github page.

Isaac designed his Tap implementation to be modular for easy consumation and extension. Taper customizes the runner component and uses the rest of node-tap as is.

Because Tap is modular, it is designed to be consumed in many ways (like automated build tools, customized runners) and other testing frameworks can provide producers to provide tap input.

Goals

  • More concise formatting of tap output (easier to find what you care about)
  • Improve ability to write to stdout and stderr from tests or code
  • Add optional colorized output

Installing

npm install taper  # install locally
# OR
npm install -g taper  # install globally

OR

Add to your project package.json:

"devDependencies" : {
  "taper" : "~0.2.0"
}

Also you will want to add a tap reporter as a devDependency to use in your tests. Try tap or tape.

Then npm install your package with dev dependencies from the project directory:

npm install

Usage

  node_modules/.bin/taper.js fileOrDir   # if installed locally
  #OR
  taper fileOrDir  # if installed globally
  #
  taper                                     # display usage
  taper --help                         # display usage
  taper --version                    # display version
  taper --no-color fileOrDir   # run without color output

Screenshots

Successful example where all tests are passing

Stderr and stdout is muted except for files which have a failing test

success-taper

Failure example with some failures and stdout

  • Green - successful tests and files
  • Red - failed tests and files
  • Blue - test names

failed-taper

Original tap runner success

success-tap

Original tap runner failure

failed-tap

Limitations

  • stdout logging that looks like tap output (ok, not ok, #) will not be displayed unless errors in file, however all stderr logging will be displayed regardless so it is recommended.
  • stdout/stderr appears before the test names and asserts due to how tap currently outputs data
  • Asserts are summarized at the bottom

License

Contributors

  • Original code Isaac Z. Schlueter [email protected] http://blog.izs.me
  • tapr by author: Jeff Barczewski (@jeffbski)
  • James Nylen (@nylen)

Contributing

  • Source code repository: https://github.com/nylen/taper
  • Ideas and pull requests are encouraged - https://github.com/nylen/taper/issues