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-diode

v1.0.2

Published

A simple node to isolate the output of a node or function to that further processing cannot affect the original.

Downloads

59

Readme

node-red-contrib-diode

Purpose

Node-Red-Contrib-Diode is a Node-Red node designed to isolate output from input. That's it, nothing more.

Reason

As messages are normally passed by REFERENCE (as against value). If passing a message from one function to another, there may be times when you want to ensure that any changes you make in the second function are not reflected back into the first - see below for more info. This node will do that for you by making a copy of your message and passing it on.

Of course, passing an object by value uses up slightly more resources than passing by reference so depending on your objects and resources you might not wish to go TOO wild with this?

Oh - and you'd want this for what reason? Should you use node-send to two outputs - and the first one passes onto a node that ALTERS say msg.payload - then your second output could find itself ALTERED! Attaching this node to the first output in these circumstances could prevent such interference.

More information

See https://tech.scargill.net/saturday-node-red-sermon for where this idea came from and why I created it. Many thanks to feedback from blog readers, MrShark for the name and of course Dave CJ of Node-Red fame for the needed function.