nodes/

Package batch provides the Batch node implementation.

Package catch provides the Catch node implementation.

Package change provides the Change node implementation.

Package comment provides the Comment node implementation.

Package complete provides the Complete node implementation.

Package csvnode provides the CSV node implementation (Node-RED type ID "csv" - named csvnode here to avoid shadowing the imported encoding/csv package within this file).

Package debug provides the Debug node implementation.

Package delay provides the Delay node implementation.

Package execnode provides the Exec node implementation (Node-RED type ID "exec" - named execnode here to avoid shadowing the imported stdlib os/exec package within this file).

Package file provides the File node implementation (Node-RED's "file" node - writes, appends to, or deletes a file).

Package filein provides the "File in" node implementation (Node-RED type ID "file in" - reads a file into the message).

Package function provides the Function node implementation.

Package htmlnode provides the HTML node implementation (Node-RED type ID "html" - named htmlnode here to avoid shadowing the imported golang.org/x/net/html package within this file).

Package httpin provides the "http in" node implementation - registers a (method, path) route on a shared HTTP listener and emits one message per matching incoming request, pairing it with a *ResponseHandle so a downstream "http response" node (internal/nodes/httpresponse) can complete it.

Package httpproxy provides the "http proxy" config node - a reusable outbound HTTP/HTTPS proxy configuration referenced by ID from other nodes (http request), rather than being wired into a flow itself (see docs/NODE_PALETTE_PLAN.md, Phase 6's config-node concept).

Package httprequest provides the "http request" node implementation - issues an outgoing HTTP request and returns the response.

Package httpresponse provides the "http response" node implementation - completes the in-flight HTTP request an upstream "http in" node (internal/nodes/httpin) paired with the message via a *httpin.ResponseHandle stored under httpin.KeyResponseHandle.

Package inject provides the Inject node implementation.

Package join provides the Join node implementation.

Package jsonnode provides the JSON node implementation (Node-RED type ID "json" - named jsonnode here to avoid shadowing the imported encoding/json package within this file).

Package junction provides the Junction node implementation.

Package linkin provides the Link In node implementation.

Package linkout provides the Link Out node implementation.

Package mqttbroker provides the "mqtt-broker" config node - a single shared paho.mqtt.golang connection, referenced by ID from mqtt in/mqtt out nodes rather than each opening its own connection (see docs/NODE_PALETTE_PLAN.md, Phase 6's config-node concept).

Package mqttin provides the "mqtt in" node implementation - subscribes to a topic on a shared mqtt-broker config node (internal/nodes/mqttbroker) and emits one message per received publish.

Package mqttout provides the "mqtt out" node implementation - publishes msg.payload to a topic on a shared mqtt-broker config node (internal/nodes/mqttbroker).

Package rangenode provides the Range node implementation (Node-RED type ID "range" - named rangenode here since "range" is a Go keyword and can't be a package name).

Package rbe provides the RBE ("report by exception") / Filter node implementation.

Package sortnode provides the Sort node implementation (Node-RED type ID "sort" - named sortnode here to avoid shadowing the imported stdlib sort package within this file).

Package split provides the Split node implementation.

Package status provides the Status node implementation.

Package switchnode provides the Switch node implementation (Node-RED type ID "switch" - named switchnode here since "switch" is a Go keyword and can't be a package name).

Package tcpin provides the "tcp in" node implementation - either listens for TCP connections (Server mode) or connects out to a remote host (client mode), emitting one message per line or per raw read from every connection.

Package tcpout provides the "tcp out" node implementation - connects out to a remote host:port and writes msg.payload, once per message (a new connection per Execute call, not a persistent one reused across messages).

Package tcprequest provides the "tcp request" node implementation - connects out, writes msg.payload, half-closes the write side (signaling EOF to the peer, the common TCP request/response idiom), and returns whatever the peer sends back before closing its own side (or before TimeoutMs/maxReplyBytes is hit).

Package template provides the Template node implementation.

Package tlsconfig provides the "tls-config" config node - a reusable TLS client/server certificate configuration referenced by ID from other nodes (http request, mqtt-broker, websocket-client), rather than being wired into a flow itself (see docs/NODE_PALETTE_PLAN.md, Phase 6's config-node concept).

Package trigger provides the Trigger node implementation.

Package udpin provides the "udp in" node implementation - listens for UDP datagrams on Port and emits one message per received datagram.

Package udpout provides the "udp out" node implementation - sends msg.payload as a single UDP datagram to Host:Port.

Package watch provides the Watch node implementation - a registry.EmittingNode with no input port that emits a message whenever one of its configured files or directories changes.

Package websocketclient provides the "websocket-client" config node - an outgoing WebSocket connection to a remote URL, referenced by ID from websocket in/websocket out (see docs/NODE_PALETTE_PLAN.md, Phase 6's config-node concept).

Package websocketin provides the "websocket in" node implementation - emits one message per message received on a shared websocket-listener or websocket-client config node (internal/nodes/websocketlistener, internal/nodes/websocketclient - either works, since both expose the same OnMessage method this node type-asserts for).

Package websocketlistener provides the "websocket-listener" config node - a server-side WebSocket endpoint mounted on the shared "http in" listener (internal/nodes/httpin), referenced by ID from websocket in/websocket out (see docs/NODE_PALETTE_PLAN.md, Phase 6's config-node concept).

Package websocketout provides the "websocket out" node implementation - sends msg.payload through a shared websocket-listener or websocket-client config node (internal/nodes/websocketlistener, internal/nodes/websocketclient).

Package xmlnode provides the XML node implementation (Node-RED type ID "xml" - named xmlnode here to avoid shadowing the imported encoding/xml package within this file).

Package yamlnode provides the YAML node implementation (Node-RED type ID "yaml" - named yamlnode here to avoid shadowing the imported yaml.v3 package within this file).