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

tap-summary

v4.0.0

Published

Summarize TAP

Downloads

8,034

Readme

tap-summary

version status dependencies devDependencies

A reporter for TAP.

Example

summary

Usage

package.json

{
  "scripts": {
    "test": "tape test/*.js | tap-summary"
  }
}

CLI Options

  --no-ansi        Disable ANSI formatting
  --no-progress    Disable progress output during tests

API

var summarize = require('tap-summary')

var fs = require('fs')
fs.createReadStream('test.tap')
  .pipe(summarize({
    ansi: true,
    progress: true,
  }))
  .pipe(process.stdout)

Also, the default formatter could be replaced with custom ones.

var reporter = require('tap-summary').reporter()

var fs = require('fs')
fs.createReadStream('test.tap')
  .pipe(customize(reporter))
  .pipe(process.stdout)

The reporter is a Duplex, which consumes the TAP input and output nothing by default. However, it emits the following events during the process, so that customize could listen to them and add something into the output.

  • reporter.on('test.start', test => {}). Fired when a new test detected.
  • reporter.on('test.end', test => {}). Fired when the end of a test reached.
  • reporter.on('test.assert', (assertion, test) => {}). Fired when a new assertion found.
  • reporter.on('summary', (stats, fails, comments) => {}). Fired when all TAP input has been processed.

Details about the test and assertion object could be found here.

The stats object:

var stats = {
  // the total time (ms) it takes
  duration: duration,
  // the total number of assertions planned
  planned: res.plans.reduce(function (p, c) {
    return c.to - c.from + 1 + p;
  }, 0),
  // the actual total number of assertions found
  assertions: res.asserts.length,
  // the number of successful assertions
  pass: res.pass.length,
  // the number of failed assertions
  fail: res.fail.length,
  // the number of comments found
  comments: res.comments.length,
}

fails will be null unless stats.fail > 0:

{ 
  testName: [failedAssertion]
}

comments will be null unless stats.comments > 0:

{ 
  testName: [comment]
}