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

whiteglove

v0.8.4

Published

Find the dirty tests making a mess of your test suite

Downloads

29

Readme

whiteglove

npm Version License Build Status Coverage Status

$ npm install -g whiteglove

Find the dirty tests making a mess of your test suite! whiteglove helps you find tests that aren't cleaning up after themselves (failing to restore stubs, polluting the global namespace) and tests that are inadvertently relying on the mess.

Usage: whiteglove <command> [options]

Commands:
  bisect <test> <directory>  find leaky tests affecting a target test
  iso <directory>            find tests that fail in isolation

Options:
  --runner, -r    Command used to run the test suite  [string] [default: "node"]
  --patterns, -p  Filename patterns matching your spec files
                                       [array] [default: [".js",".jsx",".node"]]
  --verbose       Output a ridiculous amount of information            [boolean]
  -h, --help      Show help                                            [boolean]
  -v, --version   Show version number                                  [boolean]

Examples:
  whiteglove bisect ./tests/foo.js ./tests
  whiteglove iso ./tests

whiteglove bisect

Use whiteglove bisect when you have a test that passes in isolation, but fails when run with the larger test suite. The bisect function will determine which tests are affecting your target test.

whiteglove iso

Use whiteglove iso to find tests that are inadvertently relying other leaky tests in order to pass.