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

match.flow

v0.0.1

Published

Poor man's pattern matching in flow

Downloads

6

Readme

match.flow

travis package downloads styled with prettier

Elm archiceture introduced update : (message, state) => state, Redux reducers became standard in JS, but unlike Elm JS lacks pattern matching and flow's disjoint union refinements via switch statements require ton of boilerplate. This library attempts to provide a better solution via poor man's pattern matching for flow projects.

Usage

// @flow
import match from "match.flow"

const counter = match({
  increment(_, n: number): number {
    return n + 1
  },
  decrement(_, n: number): number {
    return n - 1
  }
})

counter({ increment: true }, 5) //? 6
counter({ decrement: true }, 5) //? 4
counter({}, 5) //?

Probably the most compelling feature of this library is how it handlers error cases:

counter({ plus: 4 }, 3)

Above line would cause flow to report error below, meaning you'll catch error before your code is ever run:

Error: Readme.js:4
                           v
  4: const counter = match({
  5:   increment(_, n: number): number {
  6:     return n + 1
...:
 11: })
     ^ object literal. This type is incompatible with the expected param type of
 11:   matcher: Matcher<model, message>
                ^^^^^^^^^^^^^^^^^^^^^^^ object type. See: src/match.js:11
  Property `plus` is incompatible:
     11:   matcher: Matcher<model, message>
                    ^^^^^^^^^^^^^^^^^^^^^^^ property `plus`. Property not found in. See: src/match.js:11
                               v
      4: const counter = match({
      5:   increment(_, n: number): number {
      6:     return n + 1
    ...:
     11: })
         ^ object literal


Found 1 error

Fixing that code is as simple as providing plus case:

const counter = match({
  increment(_, n: number): number {
    return n + 1
  },
  decrement(_, n: number): number {
    return n - 1
  },
  plus(param: number, n: number): number {
    return n + param
  }
})

counter({ plus: 4 }, 3) //? 7

You could also combine multiple operations into single message although execution order is not guaranteed:

counter({ plus: 4, decrement: true }, 2) //? 5

Install

npm install match.flow