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-set-exit

v1.1.1

Published

Sets the exit code appropriately, given some tap output.

Downloads

215

Readme

tap-set-exit

Sets the correct exit code based on tap output.

Build Status npm install

Usage

Exposes a CLI tool tap-set-exit, which can be used as follows:

$ cat some-test-output.txt | tap-set-exit

Where this is most useful is running tests in an environment like jsdom or phantomjs where the correct exit code would not be set.

For an always failing test:

// file: fail.js
var test = require('tape')

test('always fails', function(t) {
  t.fail()
  t.end()
})

Run in a jsdom context after being browserified:

$ browserify fail.js | jsdom-eval | tap-set-exit

TAP version 13
# always fails 
not ok 1 (unnamed assert)

1..1
# tests 1
# pass  0
# fail  1

# ok

$ echo $?
1

Output from the tap-producing command is passed through unmodified; only the exit code is set.

License

This project is licensed under the Apache License, Version 2.0. See LICENSE for the full license.