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 🙏

© 2025 – Pkg Stats / Ryan Hefner

step-node

v0.2.1

Published

Dynamically chainable executions

Readme

step-node

Dynamically chainable executions

$ ( npm i | yarn add ) step-node

Basic usage

Import - as ES Module

import { StepNode, ActiveNode, DistributorNode } from 'step-node';

Usage

const sourceNode = new StepNode();
// defining an optional parser
sourceNode.parser = (name = 'n/a', age = 0, dob = 'n/a') => { name, age, dob };
// processor receives the node and only one input
sourceNode.processor = async (node, person) => {
  // person = { name, age, dob } received from the parser
  const { person } = await savePersonToDB(person);
  node.next(person, success);
};

const targetNode = new StepNode();
targetNode.parser = (person, saved) => { person, saved };
targetNode.processor = (node, { person, saved }) => {
  if (saved) {
    console.log('Person saved!', person);
  }
};

// wire targetNode into sourceNode
sourceNode.target = targetNode;

// start execution
sourceNode.process('John Doe', 28, '');

Or with TypeScript

interface Person {
  name: string;
  name: string;
  dob: string;
}

const sourceNode = new StepNode<{}, Person>();
sourceNode.parser = (name = 'n/a', age = 0, dob = 'n/a'): Person => { name, age, dob };
sourceNode.processor = (node: StepNode<{}, number>, input: Person): void => {
  // do something...
  node.next(/* outputs */);
}

For further usage see examples folder

Concept

Conceptually, within this library, nodes are simple processor functions that receive ONE input parameter do something and continue execution with output values. You can dynamically create a chain of node that feed data among themselves in a linear fashion - either synchronously or asynchronously.

Each node has one target node it feeds outputs into, this target can be changed dynamically, on-demand. Exception to this rule are the BroadcasterNode, RouterNode and the DistributorNode nodes, these nodes allow more scalability and /or routability to your execution. More details about node types in the next section.

Nodes can have optional parsers that can receive any number and type of arguments and compile them into one input to be processed.

Nodes can also have Scopes that allow you to persist data across multiple processes/executions.

Single-target node types

  • StepNode - base node with an optional parser, optional scope, a processor function and a target to feed outputs to
  • ActiveNode - like StepNode but you can activate or deactivate it dynamically.

Dual-target node types

  • SwapNode - like StepNode but allows dynamic swap-ing between 2 targets

Multi-target node types

Multi-target node types do not have parsers or scopes - they purely exist to allow for scalability or routability.

  • RouterNode - allows you feed your execution into a node that acts as a router whhere each route has a target node.
  • DistributorNode - allows you to add one or more target nodes to distribute processes/executions between, in a round-robin fashion.
  • BroadcasterNode - allows you to add one or more target nodes for parallel processes/execution.