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

@juliangruber/tap-finished

v0.0.2

Published

detect when tap output is finished

Downloads

2,013

Readme

tap-finished

detect when tap output is finished

build status

browser support

Normally with tap-parser the 'results' event fires only after the stream is closed. This module lets you detect whether a stream seems closed without waiting for the 'end' event.

example

Given this tap output in tap_output.txt:

TAP version 13
# wait
ok 1 (unnamed assert)
not ok 2 should be equal
  ---
    operator: equal
    expected: 5
    actual:   4
  ...

1..2
# tests 2
# pass  1
# fail  1

and given this script that pipes stdin into the finished stream:

var finished = require('tap-finished');
var stream = finished(function (results) {
    console.dir(results);
});
process.stdin.pipe(stream);

We'll use cat to create a stream that contains the tap output but doesn't end and then pipe that to the script:

$ cat tap_output.txt /dev/stdin | node stream.js 
{ ok: false,
  asserts: 
   [ { ok: true, number: 1, name: '(unnamed assert)' },
     { ok: false, number: 2, name: 'should be equal' } ],
  pass: [ { ok: true, number: 1, name: '(unnamed assert)' } ],
  fail: [ { ok: false, number: 2, name: 'should be equal' } ],
  errors: [],
  plan: { start: 1, end: 2 } }
^C

Even though the 'end' message never came, we still got the parsed results. Yay!

methods

var finished = require('tap-finished')

var ws = finished(opts={}, cb)

Return a writable stream ws that consumes tap input. cb(results) fires with the results from tap-parser when the stream seems finished or when the 'end' event occurs.

opts.wait controls how long to wait in milliseconds for more input before firing the cb if the 'end' event doesn't fire.

install

With npm do:

npm install tap-finished

You can use this module in the browser with browserify.

license

MIT