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

@briandamaged/dispatcher

v1.0.0

Published

Command Dispatcher

Downloads

7

Readme

js-dispatcher

Flexible Conditional Logic

Usage

The Basics

Here's an example of a programmatically constructed if... else if... else statement:

const {
  Dispatcher,
  IF, RETURN,
} = require('js-dispatcher');


const d = Dispatcher();

// Setup our Dispatcher rules:
d.use(IF((x, y)=> x < y, (x, y)=> x + y));
d.use(IF((x, y)=> x > y, (x, y)=> x * y));
d.otherwise((x, y)=> 0);


// Alright, let's put it to the test:
console.log(d(3, 4));   // Output: 7
console.log(d(4, 3));   // Output: 12
console.log(d(3, 3));   // Output: 0

Notice that d.otherwise((x, y)=> 0) always just returns the value 0. Since this is a common pattern, you can also write the statement as:

d.otherwise(RETURN(0));

Advanced Stuff

The IF(condition, handler) function is just a factory for producing a very common type of RULE_FUNCTION. Specifically, the RULE_FUNCTION has the form:

function _if(...args) {
  if(condition(...args)) {
    return handler;
  }
}

As you can see, it evaluates the condition(..). If this condition returns something truthy, then it returns the associated handler(..) function. Otherwise, it returns undefined. This protocol informs the Dispatcher about whether or not the RULE_FUNCTION is able to handle the input.

Most of the time, you don't need to worry about this level of detail, and you can just rely upon the IF(..) factory. But, on rare occassions, both the RULE_FUNCTION and the handler(..) function rely upon the same computationally-expensive operation. In these cases, you can write your own RULE_FUNCTION by hand to minimize computational costs. For example:

function customRule(...args) {
  const expensive = someExpensiveCalculation(...args);

  if(someCondition(expensive)) {
    function handler() {
      return doSomethingWith(expensive);
    }

    return handler;
  }
}


d.use(customRule);