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

cases-conds

v1.0.0

Published

Fluent interfaces to map cases to results, based on a test value

Downloads

8

Readme

Cases Conds

Use the conds expression to examine an object and return a corresponding result:

import { conds } from 'cases-conds';

const TEMPERATURE = 12;

const result = conds(TEMPERATURE)
  .when(t => t < 0, 'Too low')
  .when(t => t > 39, 'Too high')
  .when(isNaN, 'Unknown temperature')
  .otherwise('Alright');

// result => 'Alright'

It also supports lazy results:

import { conds } from 'cases-conds';

const TEMPERATURE = 12;

const result = conds(TEMPERATURE)
  .when(t => t < 0, () => 'Too low')
  .when(t => t > 39, () => 'Too high')
  .when(isNaN, () => 'Unknown temperature')
  .otherwise(() => 'Alright');

// result => 'Alright'

Lazy results are the way to throw errors:

import { conds } from 'cases-conds';

const TEMPERATURE = 12;

const result = conds(TEMPERATURE)
  .when(t => t < 0, () => 'Too low')
  .when(t => t > 39, () => 'Too high')
  .when(isNaN, () => { throw new Error('Unknown temperature'); })
  .otherwise(() => 'Alright');

// result => 'Alright'

You can use the input object from the expression's head as part of the results:

import { conds } from 'cases-conds';

const TEMPERATURE = 12;

const result = conds(TEMPERATURE)
  .when(t => t < 0, () => 'Too low')
  .when(t => t > 39, () => 'Too high')
  .when(isNaN, () => { throw new Error('Unknown temperature'); })
  .otherwise(t => t + ' is alright');

// result => '12 is alright'

There are situations in which using object literals to enable pattern matching has limitations:

const checkboxGroup = {
  false: 'None selected',
  undefined: 'Some selected',
  true: 'All selected'
};

const result = checkboxGroup[undefined];

// Error: undefined cannot be used in indexer

However, you can achieve the desired behavior with the cases expression:

import { cases } from 'cases-conds';

function getResult(checked?: boolean) {
  return cases(checked)
    .when(false, 'None selected')
    .when(undefined, 'Some selected')
    .otherwise('All selected');
}

const result = getResult(undefined);

// result => 'Some selected'

The previous example wraps the cases expression into a function just to demonstrate the use of an union type. In real code, wrapping may be unnecessary.