`lazy-pipeline`

A super light-weight, tree-shakeable, reusable, lazy pipeline TypeScript library with functional APIs and no 3rd-party dependencies.

lazy-pipeline package is already tiny, but with its tree-shakeable design, the final package size will be reduced much more by the build tool.

Installation

npm i -S lazy-pipeline

What is a reusable, lazy pipeline?

Consider the following common pattern with arrays

const source = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]; // 10 elements

source
  .map(value => value + 1) // Iterate 10 times and add 1 to each number each time
  .filter(value => value % 2 === 0) // Iterate 10 times and filter out any odd numbers
  .reduce((left, right) => left + right); // Iterate 5 times and sum up the numbers

The combination of map, filter, and reduce operations above constitutes a pipeline, each operation executes eagerly as soon as it is added, but most notably, each operation runs as many times as there are elements.

The example above would look similar to the following using for-of loops:

const source = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9];

// map(value => value + 1)
const mappedValues = [];
for (const value of source) {
  mappedValues.push(value + 1);
}

// filter(value => value % 2 === 0)
const filteredValues = [];
for (const value of mappedValues) {
  if (value % 2 === 0) {
    filteredValues.push(value);
  }
}

// reduce((left, right) => left + right)
let sum = 0;
for (const value of filteredValues) {
  sum += value;
}

As you can see, it needs to iterate through the entire array every time an operation (map, filter, and reduce) is added which is not something that we want.

Now consider a similar pipeline using lazy-pipeline APIs.

import { LazyPipeline } from 'lazy-pipeline';
import { filter, map, peek } from 'lazy-pipeline/operators';
import { sum } from 'lazy-pipeline/collectors';

const source = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9];

const result = LazyPipeline.from(source) // Creating a new pipeline object
  // Begin adding operations to this pipeline
  .add(
    /*
     * `peek()` allows to perform some action on each pipeline element with no transformations applied to it,
     * here we're logging each element to verify that we're only iterating over `source` 10 times
     */
    peek(value => console.log(value)),

    // Adding a mapping stage, incrementing each number by 1
    map(value => value + 1),

    // Adding a filtering stage, discarding any odd numbers
    filter(value => value % 2 === 0)
  )
  // Telling the pipeline to start executing all of the added stages (operations)
  .collect(
    // Adding a terminal stage that sums all elements in the pipeline and return the result to the caller
    sum()
  );

console.log(result); // Outputs 30

This second example is no different than the first one in terms of the final result, however, there are a few things that distinguish it from the first example. First of all, you can add as many intermediate stages (map, and filter or any intermediate stages) to the pipeline, those stages won't be executed until collect() is called, that's the reason for its lazy evaluation nature, collect() expects a terminal stage which is the final stage to produce the result, these terminal stages' sole responsibility is to collect the remaining pipeline elements into some final result container. Second of all, all stages (map, filter and sum in this example) run in the same iteration which is much more efficient as compared to the first example, the second example would look similar to the following with a regular for-of loop:

const source = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9];

let sum = 0;
for (const value of source) {
  // peek(...)
  console.log(value);

  // map(...)
  const mappedValue = value + 1;

  // filter(...)
  if (mappedValue % 2 === 0) {
    // sum()
    sum += mappedValue;
  }
}

console.log(sum);

As you can see, we only need to iterate once per element to evaluate all of our operations which is obviously much more efficient.

The most interesting bit of lazy-pipeline module is its reusability feature. After constructing your pipeline, and adding any number of intermediate stages to it, you can pass this pipeline object around and reuse it on as many iterable data sources as desired, but keep it mind that after each call to collect() to get the result, the pipeline will be frozen to prevent any new stages from being added to it, to unfreeze it, simply call unfreeze() on the same pipeline instance, for example:

import { LazyPipeline } from 'lazy-pipeline';
import { filter, map, skip } from 'lazy-pipeline/operators';
import { findFirst, findLast, max, min } from 'lazy-pipeline/collectors';

const source1 = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9];

const pipeline = LazyPipeline.from(source1).add(
  map(value => value + 1), // (1)
  filter(value => value % 2 === 0) // (2)
);

const maxNumber = pipeline.collect(
  /*
   * max() collector returns a terminal stage that finds the max number by default, if elements in the pipeline
   * are not numbers, then you must provide a comparator to `max()` to return the max element.
   */
  max()
);

// Calling resume() is required before reusing the same pipeline instance
pipeline.resume();

// Calling unfreeze() so that we can add new stages to this pipeline, otherwise, it will throw an error
pipeline.unfreeze();

const minNumber = pipeline
  .add(
    // map(...) and filter(...) from (1) and (2) will execute before this new limit(5) stage
    limit(5) // (3)
  )
  .collect(
    /*
     * min() collector returns a terminal stage that finds the min number by default, if elements in the pipeline
     * are not numbers, then you must provide a comparator to `min()` to return the min element.
     */
    min()
  );

// Calling resume() again so that we can calculate a new result
pipeline.resume();

// Have to unfreeze so that we can add a new `skip()` stage to it
pipeline.unfreeze();

// The pipeline instance will execute the same source `source1` passed to `LazyPipeline.from(...)` above
const firstElement = pipeline
  .add(
    // map(...), filter(...) and limit(...) from (1), (2), and (3) will execute before skip(2) does
    skip(2) // (4)
  )
  .collect(
    /*
     * findFirst() returns the very first element in the pipeline, or `undefined` when pipeline has no elements
     */
    findFirst() // (5)
  );

// We have to call `resume()` anytime we need to calculate a new result
pipeline.resume();

const source2 = [1, 10, 100, 1000, 10000];
/*
 * Because we want to use `source2` instead of `source1` that was passed to `LazyPipeline.from()` above,
 * we're calling `readFrom()` on `pipeline` to switch to a different data source. From this point on,
 * `pipeline` will use `source2` as the data source to read elements from.
 */
pipeline.readFrom(source2);

// Because we don't need to add new stages to this pipeline, we didn't call `unfreeze()` on it

const lastElement = pipeline.collect(
  /**
   * `findLast()` collector finds and retrieves the very last element in the pipeline, if the pipeline has no
   * elements, `undefined` is returned.
   */
  findLast()
);

Once again, all stages (1), (2), (3), (4) and (5) from the example above will all run in the same iteration.

Terminologies

Pipeline: A series of stages that execute in order and in the same iteration, and end with a terminal stage that returns a result. Once the pipeline has been consumed by triggering a terminal stage with collect(), it cannot be consumed again until resume() is called, otherwise, the pipeline will throw an error to indicate as such.
Stage: A particular operation that executes on each element in the pipeline.
Intermediate stage: A stage that performs some transformation on each element in the pipeline and forwards the new element to the next stage in line downstream. The built-in intermediate stages' creators are located inside operators module.
Terminal stage: The final stage that collects all remaining elements in the pipeline to produce a result. Each pipeline doesn't execute until a terminal stage is triggered by calling collect() on the pipeline instance which expects a TerminateStage object. Terminal stages' creators are located inside collectors module.
Collector: A function that returns a new object instance of type TerminalStage.
Operator: A function that returns a new object instance of type IntermediateStage.

Advantages of tree-shakeable, functional APIs

All of the stages (intermediate and terminal) are created using standalone functions, this not only makes the APIs easier to use, it also allows bundling tools to effortlessly tree-shake those functions that are not imported into your application. Additionally, with a functional programming model, it's straightforward to extend this library with your own operators and collectors.

How to add a new operator

To add a new operator, create a function that returns a new object instance of type IntermediateStage each time it's called.

As an example, let's create an operator that increments each number in the pipeline by some provided value:

import { IntermediateStage } from 'lazy-pipeline/stages';

class IncrementByStage<IN extends number> extends IntermediateStage<IN, number> {
  constructor(private readonly _valueToIncrementBy: number) {
    super();
  }

  override consume(element: IN, hasMoreDataUpstream: boolean): void {
    this._throwErrorIfNotNumber(element);
    this._downstream.consume(element + this._valueToIncrementBy, hasMoreDataUpstream);
  }

  private _throwErrorIfNotNumber(element: IN) {
    if (typeof element !== 'number') {
      throw new Error(
        `[incrementBy() operator] Numbers expected, erroneous pipeline element received was ${JSON.stringify(element)}`
      );
    }
  }
}

/**
 * Return an intermediate stage that increments each pipeline numeric element by `value`,
 * if at least one element is not numeric, then an error will occur.
 *
 * @param value The value to increment each element by
 * @returns
 */
export function incrementBy<IN extends number>(value: number): IntermediateStage<IN, number> {
  if (typeof value !== 'number') {
    throw new Error(
      `[incrementBy() operator] The provided value to increment by is not a number, it was ${JSON.stringify(value)}`
    );
  }
  return new IncrementByStage<IN>(value);
}

To use the new operator, simply add it to the pipeline, for example:

import { LazyPipeline } from 'lazy-pipeline';
import { sum } from 'lazy-pipeline/collectors';

import { incrementBy } from './incrementBy';

const result = LazyPipeline.from([1, 2, 3, 4, 5]).add(incrementBy(10)).collect(sum());

To view all built-in operators, please see the operators module

How to add a new collector

To add a new collector, create a function that returns a new object instance of type TerminalStage each time it's called. Each terminal stage must additionally implement get() method to return the final result when the pipeline terminates.

As an example, let's create a collector that multiplies all numbers in the pipeline:

import { TerminalStage } from 'lazy-pipeline/stages';

class MultiplyStage<IN extends number> extends TerminalStage<IN, number> {
  private _product = 1;

  override consume(element: IN, hasMoreDataUpstream: boolean): void {
    this._throwErrorIfNotNumber(element);
    this._product *= element;
  }

  private _throwErrorIfNotNumber(element: IN) {
    if (typeof element !== 'number') {
      throw new Error(
        `[multiply() collector] Numbers expected, erroneous pipeline element received was ${JSON.stringify(element)}`
      );
    }
  }

  override get(): number {
    return this._product;
  }
}

/**
 * Return a terminal stage that multiplies all pipeline elements together, if some element
 * is not numeric, then an error will occur.
 *
 * @param value The value to increment each element by
 * @returns
 */
export function multiply<IN extends number>(): IntermediateStage<IN, number> {
  return new MultiplyStage<IN>(value);
}

To use the new collector, simply provide it to collect() as followed:

import { LazyPipeline } from 'lazy-pipeline';
import { filter, map } from 'lazy-pipeline/operators';

import { multiply } from './multiply';

const result = LazyPipeline.from([1, 2, 3, 4, 5])
  .add(
    filter(e => e % 2 === 0),
    map(e => e * e)
  )
  .collect(multiply());

To view all built-in collectors, please see the collectors module

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

README.md

README.md

`lazy-pipeline`

Installation

Table of contents

What is a reusable, lazy pipeline?

Terminologies

Advantages of tree-shakeable, functional APIs

How to add a new operator

How to add a new collector

Files

README.md

Latest commit

History

README.md

File metadata and controls

lazy-pipeline

Installation

Table of contents

What is a reusable, lazy pipeline?

Terminologies

Advantages of tree-shakeable, functional APIs

How to add a new operator

How to add a new collector

`lazy-pipeline`