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

@flowfuse/nr-project-nodes

v0.6.4

Published

A collection of Node-RED nodes for easy communication between Node-RED instances running in the FlowFuse platform

Downloads

2,977

Readme

FlowFuse Project Nodes

A collection of Node-RED nodes for easy communication between Node-RED instances running in the FlowFuse platform.

These nodes act in a similar way to the core Node-RED Link nodes - but can be used to send and receive messages between different Node-RED instances and devices.

Whilst these nodes are published under the Apache-2.0 license, they can only be used with an instance of the FlowFuse platform with an active EE license applied. If you try to install these nodes in an Non FlowFuse EE platform you will see the following error in your Node-RED log: Error: Project Link nodes cannot be loaded outside of FlowFuse EE environment This can be safely ignored.

Prerequisites

  • FlowFuse 0.8+ running with an active EE license and its integrated MQTT Broker
  • FlowFuse 1.14+ for communicating with application assigned devices

Alternatively, you can sign up to FlowFuse Cloud now to try these nodes out.

Nodes

There are three nodes in this collection:

  • Project In - listens for messages being broadcast by other Node-RED instances, or for messages being sent just to this instance
  • Project Out - sends messages to other Node-RED instances
  • Project Call - sends messages to other Node-RED instances and waits for a response

The nodes send the whole msg object. Due to the way the nodes encode messages, there are some data types that do not get sent. For example, the msg.req/msg.res properties used by the core HTTP nodes will not be sent. Instead, they are temporarily removed from the message and re-attached when the message is received back.

Each node is configured with a topic on which it either sends or receives messages on. This is similar in concept to MQTT topics - although the nodes do not currently support using MQTT wildcards in their topics.

The Project Out nodes can either broadcast messages on a topic to anyone listening, or they can send messages on a topic to a specific other project.

The Project In nodes do the opposite - they can either listen for messages being broadcast, or for messages sent directly to them.

The Project Call node can be used to send a message to another Project In node and then wait for a response, with a built-in timeout if it doesn't arrive. The response is sent back using a Project Out node configured to respond to the call node.