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-console-parser

v1.0.4

Published

parses tap by hijacking console.log

Downloads

297

Readme

tap-console-parser

stable

Parses TAP by hijacking console.log, primarily useful for colorizing tests in the browser console.

var parser = require('tap-console-parser')

// start hijacking console.log()
var tap = parser()

// we can print to the real console with log()
tap.on('assert', function (assert) {
  tap.log('Got assert!', assert.name)
})

// get result
tap.on('complete', function (result) {
  // stop hijacking console.log
  tap.detach()
  
  if (result.ok)
    console.log('Ok!')
  else
    console.log('Not ok!')
})

Usage

NPM

parser = tapConsole()

Creates a new TAP parser and hijacks the global console.log function.

parser.attach()

Hijacks the console.log function. Any subsequent logs will be captured by this parser and not printed to the native console.

parser.detach()

Un-hijacks the console.log function. Subsequent logs will not be parsed, and will be passed to the native console as usual.

parser.log(args)

The native console.log() function, can be used while the parser is attached to actually log something to the console.

parser.on('assert', fn)

Called when an assertion is met, see tap-out#assert.

parser.on('test', fn)

Called when a new test block is met, see tap-out#test

parser.on('complete', fn)

Called when tests, fail and pass have been parsed, and we can assume the test is over. The passed parameter looks like:

{
  ok: false,
  total: 3,
  pass: 2,
  fail: 1
}

parser.on('log', fn)

Called whenever console.log() is called with args, an array of the user's arguments. It allows you to pass along logs to the native console like so:

parser.on('log', function(args) {
  parser.log.apply(null, args)
})

License

MIT, see LICENSE.md for details.