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 🙏

© 2024 – Pkg Stats / Ryan Hefner

faucet

v0.0.4

Published

human-readable TAP summarizer

Downloads

138,109

Readme

faucet

human-readable TAP summarizer

example

Pipe TAP text into the faucet command, get back pretty results:

piping tap

You can use any runner you want to generate the TAP output. Here we'll use tape:

tape runner

You can give the faucet command a list of files:

list of files

or if you just type faucet, any js files in test/ or tests/ will be run using the tape command internally:

implicit test/ directory

install

To get the faucet command, with npm do:

npm install -g faucet

generating TAP

The great thing about TAP is that it's inherently serializable on stdout, so you can use whichever libraries you wish to generate it.

Many test libraries have ways to get TAP output.

tape and tap will give you TAP output by default.

With a tape test, you would just write a test.js like:

var test = require('tape');

test('beep boop', function (t) {
	t.plan(2);

	t.equal(1 + 1, 2);
	setTimeout(function () {
		t.deepEqual(
			'ABC'.toLowerCase().split(''),
			['a','b','c']
		);
	});
});

and then just run the file with node test.js to get the TAP output:

TAP version 13
# beep boop
ok 1 should be equal
ok 2 should be equivalent

1..2
# tests 2
# pass  2

# ok

or if you have a directory of files, you can use the tape command that you get when you npm install -g tape:

$ tape test/*.js
TAP version 13
# stream in a stream
ok 1 should be equivalent
# expand a streams1 stream
ok 2 should be equivalent
# expand a streams2 stream
ok 3 should be equivalent
# expand a streams2 stream with delay
ok 4 should be equivalent

1..4
# tests 4
# pass  4

# ok

To get TAP out of mocha, do mocha -R tap:

$ mocha -R tap
1..17
ok 1  shim found
ok 2  core shim not found
ok 3  false file
ok 4  false module
ok 5  local
ok 6  index.js of module dir
ok 7  alternate main
ok 8  string browser field as main
ok 9  string browser field as main - require subfile
ok 10  object browser field as main
ok 11  object browser field replace file
ok 12  object browser field replace file - no paths
ok 13  replace module in browser field object
ok 14  replace module in object browser field with subdirectory
ok 15  replace module in object browser field with subdirectory containing
package.json
ok 16  replace module in object browser field with subdirectory containing
package.json with string browser field as main
ok 17  replace module in object browser field with subdirectory containing
package.json with object browser field as main
# tests 17
# pass 17
# fail 0

Once you've got a way to get TAP out of your tests, just pipe into faucet:

mocha pipe

usage

usage:
  faucet [FILES]
  command | faucet

license

MIT