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

basicset-shunt

v1.0.0

Published

An operation dispatcher.

Downloads

2

Readme

basicset-shunt

Dispatches/routes operations. For APIs that support batch operations. e.g. Saving a document and retrieving another document in one call.

Installation

npm install basicset-shunt

Usage

First, you create the shunt object.

var createShunt = require('basicset-shunt');
var aShunt = createShunt();

Then, you define operatives, which are function that carry out the work of the operations.

aShunt
  .addOperative('sumUpArray', function(params, done, prevOpResult) {
    var value = params.reduce(
      function add(sum, next) { return sum + next; }, 0
    );
    done('Added', value);        
  })
  .addOperative('multiplyArray', function(params, done, prevOpResult) {
    var value = params.reduce(
      function multiply(product, next) { return product * next; }, 1
    );
    done('Multiplied', runningProduct);
  })
  .addOperative('delayNumberReturn', function(params, done, prevOpResult) {
    setTimeout(function giveNumber() {
      done('Gave back', params.number);
    },
    params.delay);
  });

addOperative tells shunt which functions map to which string keys. Each operative is expected to have a function signature that takes:

  1. params, which can be anything
  2. done, a callback function which takes an error and whatever value the operative wants to report.
  3. prevOpResult, which is the result object (explained further down) from the previous operation in the sequence. This could be null.

Finally, you call runSequenceGroup, passing it:

  1. opSequenceGroups: An array of arrays containing operation objects. Each subarray is a sequence. The operations in that sequence are guaranteed to run one after another, and each operation will have access to the result of the previous one.

The sequences themselves do not run in a guaranteed order. If you have a bunch of operations you want to run and don't care about order, you can pass an array of arrays, each of which has only one operation object.

  1. writableStream: A writable stream in object mode. runSequenceGroup will write result objects (the results of the operations) to it as it produces them.

     var resultStream = Writable({objectMode: true});
     resultStream._write = function reportResult(result, encoding, next) {
       console.log('id:', result.id);
       console.log('error:', result.error);
       console.log('value:', result.value);
       next();
     };
     resultStream.on('finish', function reportDone() {
       console.log('All done with operations.');
     });
     shunt.runSequenceGroup([
       [
         {
           id: 'op1',
           op: 'delayNumberReturn',
           params: [3, 4, 5, 10]
         },
         {
           id: 'op2',
           op: 'multiplyArray',
           params: [1000, 0.5]
         }
       ],
       [
         {
           id: 'op3',
           op: 'sumUpArray',
           params: [800, -45]
         }
       ]
     ],
     resultStream);

Operation objects

Each operation object should have these properties:

  • id: A unique identifier that the client can use to match results to the requestion operations.
  • op: A string indicating the operative to use to execute the operation.
  • params: The params to pass to the operative. Can be anything the operative expects.

Result objects

Result objects properties:

  • id: An identifier that matches the operation object that was used to produce this result.
  • error: An error object.
  • value: The result of the operation.

Tests

Run tests with make test.

License

The MIT License (MIT)

Copyright (c) 2015 Jim Kang

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.