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

node-red-contrib-latching-router

v1.0.3

Published

A simple routing node that will latch the output and route all subsequent messages to that output.

Downloads

20

Readme

node-red-contrib-latching-router

A simple routing node that will latch the output and route all subsequent messages to that output.

E.g. Drag the node into your workspace and configure it to have 3 outputs. Send a string payload of latchOutput 3 to the node. This will cause the node to route all subsequent messages to output 3.

Outputs are not zero indexed. So latchOutput 1 will route subsequent messages to the 1st output.

Messages which alter the latch are consumed and do not get sent via an output.

Installation

Change directory to your node red installation:

$ npm install node-red-contrib-latching-router

Configuration

There isn't much to configure. Choose the number of outputs you need. The minimum is 2 as it makes no sense to only have 1 output for this node.