.js file defines the runtime behaviour of the node.
Nodes are defined by a constructor function that can be used to create new instances of the node. The function gets registered with the runtime so it can be called when nodes of the corresponding type are deployed in a flow.
The function is passed an object containing the properties set in the flow editor.
The first thing it must do is call the
RED.nodes.createNode function to initialise
the features shared by all nodes. After that, the node-specific code lives.
Nodes register a listener on the
input event to receive messages from the
up-stream nodes in a flow.
Nodes can send messages to the down-stream nodes in a flow using the
msg is null, no message is sent.
If the node has more than one output, an array of messages can be passed to
each one being sent to the corresponding output.
It is possible to send multiple messages to a particular output by passing an array of messages within this array:
Whenever a new flow is deployed, the existing nodes are deleted. If any of them
need to tidy up state when this happens, such as disconnecting
from a remote system, they should register a listener on the
If the node needs to do any asynchronous work to complete the tidy up, the registered listener should accept an argument which is a function to be called when all the work is complete.
If a node needs to log something to the console, it can use one of the follow functions:
error messages also get sent to the flow editor debug tab.
If the node encounters an error that should halt the current flow, it should log
the event with the
If the error is one that a user of the node may want to handle for themselves, the function should be called with the original message (or an empty message if this is an Input node) as the second argument:
This will trigger any Catch nodes present on the same tab.
Whilst running, a node is able to share status information with the editor UI.
This is done by calling the
The details of the status api can be found here.