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 🙏

© 2026 – Pkg Stats / Ryan Hefner

call-the-whole-thing-off

v0.0.2

Published

making if (a || b) easier

Downloads

23

Readme

Let's Call the Whole Thing Off

♪ You say /ˈiːð.ə(ɹ)/ and I say /ˈaɪð.ə(ɹ)/ ♪

What is this thing?

Have you ever been writing code like this:

if (a || b) {
    // which one was it?
}

...and wanted to get which value was eventually used in your || OR statement?

Well, Let's Call the Whole Thing Off is for you!

How do I download it?

Through the magic of npm:

NPM

How do I use it?

It's simple!

var either = require('call-the-whole-thing-off');

var a = "I'm an example!";
var b = false;
if (either(b, a)) {
    console.log(either.which()); // "I'm an example!"
}

Just replace your || statement with either(a, b, c.... So for if (oh || my || god), you would put if (either(oh, my, god)). Magic™!

But what if there's more than one true statement?

either() will take the first statement that is true (would pass an if ()) and make it available to either.which(). You can also use either.all(), which will return all true statements in an array:

if (either.all(true, true, true)) {
    console.log(either.which()) // [true, true, true]
}

Can I have some tests?

Sure:

$ npm test

(you might need to npm install first to install the mocha devDependency)

What's the license?

ISC. I'm pretty relaxed about licensing anyway.