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 🙏

© 2025 – Pkg Stats / Ryan Hefner

eslint-plugin-no-boolean-switch

v0.1.2

Published

ESLint rule for disallow using boolean literals as switch statement arguments

Readme

eslint-plugin-no-boolean-switch

NPM Version

Adds eslint rules to disallow using boolean literals as switch statement arguments

Necessity

You should avoid such constructions, because they contain logical errors

const x = 1;

switch (true) {
  case !!x:
    console.log('logging first case');
    break;
  case x === 1:
    console.log('logging second case');
    break;
}

Let's use an example to see how switch(true) can be rewritten more safely

Was:

function getNodeDescriptionSwitch(node: Node) { 
  switch (true) { 
    case isArrayLiteralExpression(node): 
    case isObjectLiteralExpression(node): 
      return "Array or object"; 
    case isBigIntLiteral(node): 
    case isNumericLiteral(node): 
      return "Numberish"; 
    case isNoSubstitutionTemplateLiteral(node): 
    case isRegularExpressionLiteral(node): 
    case isStringLiteral(node): 
    case isTemplateLiteral(node): 
      return "Stringlike"; 
    default: 
      return "Some sort of node"; 
  } 
}

Became:

function getNodeDescriptionSwitch(node) {
  if (isArrayLiteralExpression(node) || isObjectLiteralExpression(node)) {
    return "Array or object";
  } else if (isBigIntLiteral(node) || isNumericLiteral(node)) {
    return "Numberish";
  } else if (
    isNoSubstitutionTemplateLiteral(node) ||
    isRegularExpressionLiteral(node) ||
    isStringLiteral(node) ||
    isTemplateLiteral(node)
  ) {
    return "Stringlike";
  } else {
    return "Some sort of node";
  }
}

Installation

npm i -D eslint-plugin-no-boolean-switch

Usage

Add no-switch-boolean to your .eslintrc configuration.

{
  "plugins": ["no-boolean-switch"]
}
{
  "rules": {
    "no-boolean-switch/no-boolean-switch": "warn"
  }
}

Changelog

0.1.2

  • Adding installation and usage example to Readme.md

0.1.1

  • Delete eslint package from peerDependencies
  • Added the correct readme.md
  • Set the package version to the semantically correct one

0.0.1

  • Initial Release