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

@citrus327/match

v1.0.0

Published

My awesome typescript library

Downloads

1

Readme

match

Download Version

A basic JavaScript version of Rust pattern matching.

Installation

pnpm install @citrus327/match --save

Usage

checkout tests for more examples.

Basic

import { match, _ } from '@citrus327/match';

function t1 () {
  const a = "hello"
  const result = match(a, [
    ["hello", () => 1],
    ["world", () => 2],
    [_, () => null],
  ])
  console.log(result === 1) // true
}

with Typescript Enum

import { match, _ } from '@citrus327/match';

function t1 () {
  enum Flag {
    Yes = 1,
    No = 2,
  }
  const flag = Flag.Yes
  const result = match(flag, [
    [Flag.Yes, () => "YES"],
    [Flag.No, () => "NO"],
  ])
  console.log(result === "YES") // true
}

Rules

  1. if multiple matchers found, match will only match the first one (same as fallback matchers).
  2. must contain a fallback matcher, match will throw if no fallback matcher found.

These two rules are followed by Rust's implementation.

Comparison

  • In Rust
fn main() {
  let number = 1;
  match number {
      1 => println!("One!"),
      _ => println!("Ain't special"),
  }

  let boolean = true;
  let binary = match boolean {
      false => 0,
      true => 1,
  };

  println!("{} -> {}", boolean, binary);
}
// output: 
// One!
// true -> 1
  • In Javascript
import { match, _ } from '@citrus327/match';

function main () {
  let number = 1;
  match(number, [
    [1, () => console.log("One!")],
    [_, () => console.log("Ain't special")]
  ])

  let boolean = true;
  let binary = match(boolean, [
    [false, () => 0],
    [true, () => 1],
  ])

  console.log(`${boolean} -> ${binary}`);
}
// output: 
// One!
// true -> 1