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

@lebedevna/match

v0.1.0

Published

Tiny TypeScript helpers for exhaustive matching on string unions.

Readme

@lebedevna/match

Tiny TypeScript helpers for exhaustive matching on string unions.

@lebedevna/match gives you two small utilities:

  • match for mapping a string union to a value
  • matchf for mapping a string union to a function and executing only the selected branch

The API is intentionally minimal. It uses TypeScript's type system to require a case for every member of the union.

Install

npm install @lebedevna/match

Usage

match

Use match when each branch returns a plain value.

import { match } from "@lebedevna/match";

type Status = "idle" | "loading" | "success" | "error";

const status: Status = "success";

const label = match(status, {
  "idle": "Idle",
  "loading": "Loading...",
  "success": "Done",
  "error": "Failed",
});

Because the second argument is Record<T, TValue>, TypeScript requires every possible key from T.

type Theme = "light" | "dark";

const className = match<Theme, string>("light", {
  "light": "theme-light",
  "dark": "theme-dark",
});

matchf

Use matchf when branch logic should run lazily.

import { matchf } from "@lebedevna/match";

type Role = "guest" | "user" | "admin";

const role: Role = "admin";

const permissions = matchf(role, {
  "guest": () => ["read"],
  "user": () => ["read", "comment"],
  "admin": () => ["read", "comment", "write", "delete"],
});

This is useful when branches are expensive, have side effects, or are easier to express as separate functions.

Why use this

  • Exhaustive by type: missing cases fail at compile time
  • Tiny surface area: two functions, no DSL
  • Works well with string literal unions
  • matchf avoids evaluating unused branches

API

function match<T extends string, TValue>(
  value: T,
  variants: Record<T, TValue>,
): TValue;

function matchf<T extends string, TValue>(
  value: T,
  variants: Record<T, () => TValue>,
): TValue;

Notes

  • value must be typed as a string literal union for exhaustive checking to be useful
  • The helpers do not provide a fallback branch; every case must be present
  • These helpers are designed for TypeScript, not runtime validation of arbitrary input

License

MIT