Registry / messaging / node-red-contrib-qrusty

node-red-contrib-qrusty

library0.21.0jsnpmunverified

Node-RED custom nodes for the Qrusty priority queue server. Current stable version 0.21.0, released on npm with minor updates. Provides 17 drag-and-drop action nodes (publish, consume, ack, nack, queue management, observability) plus a shared config node, fully typed with HTML templates. Key differentiator: eliminates hand-written `function` nodes by wrapping the `qrusty-client` npm package in native Node-RED editor nodes with config-vs-msg fallback. Requires Node.js >= 18 and Node-RED >= 3.0.

messaging devops

npm install node-red-contrib-qrusty

package ↗homepage ↗

INSTALL

IMPORT

SIG · NODE-RED-CONTRIB-Q

node-red-contrib-qrusty

messagingjavascriptv0.21.0

harness data pending

Install & Compatibility

Where this runs

No compatibility data collected yet for this library.

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

QrustyServerNode

✓ // not directly importable; configured via editor

Nodes are registered by Node-RED runtime; no direct JavaScript import. Use palette manager or require('node-red-contrib-qrusty') in Node-RED settings.

node-red-contrib-qrusty

✓ require('node-red-contrib-qrusty')

✗ import * as qrusty from 'node-red-contrib-qrusty'

Node-RED node packages are CommonJS; ESM import is not supported by Node-RED runtime.

Shows how to install and use the nodes in Node-RED: install package, configure server, publish a message.

// This package is not imported directly; it's installed and used via Node-RED UI. // To install: in your Node-RED user directory (typically ~/.node-red), run: // npm install node-red-contrib-qrusty // Then restart Node-RED. A new "qrusty-server" config node and 18 node types will appear in the palette. // 1. Drag a "qrusty-server" config node onto the workspace, set host/port. // 2. Drag a "qrusty-publish" node, set the server config, queue name, and msg.payload. // 3. Inject a message and deploy. The node will POST /publish to Qrusty.

Debug

Known issues

breakingRequires Node.js >= 18 and Node-RED >= 3.0. Older Node.js versions will fail to install or run.

fix

Upgrade Node.js to >=18 and Node-RED to >=3.0.

affects: <0.18.0

gotchaConfig-vs-msg fallback: if you set a field in the editor panel, it takes precedence over msg properties. Leave blank to allow runtime values from msg.

fix

Ensure editor fields are empty if you intend to pass values via msg.

affects: *

gotchaBatch nodes (ack-batch, nack-batch) expect msg.payload to be an array of strings (message IDs). Non-array payload will cause HTTP 400.

fix

Ensure msg.payload is an array of strings before batch nodes.

affects: *

deprecatedNode names have stabilized; early alpha releases used different naming conventions.

fix

Upgrade to latest 0.21.0 for consistent node names.

affects: <0.10.0

Errors

Common errors & fixes

Error: Cannot find module 'node-red-contrib-qrusty'

npm install run from wrong directory (not ~/.node-red) or package not installed.

fix

Navigate to your Node-RED user directory (e.g. cd ~/.node-red) and run npm install node-red-contrib-qrusty.

SyntaxError: Unexpected token ... (or similar node version error)

Node.js version <18 does not support optional chaining or other ES2020 features used by the package.

fix

Upgrade Node.js to version 18 or newer.

Qrusty Server not configured: no qrusty-server config node selected

Action node's server config is not set or not deployed.

fix

Open the action node, select an existing qrusty-server config node (or create one), then click Done and Deploy.

Upgrade

Version history

0.21.0latest on npm

Audit

Dependencies

node-redrequiredpeer dependency — required at runtime to load nodes

qrusty-clientrequiredunderlying HTTP client for the Qrusty server API

Agent activity

5 hits · last 30 days

node

OpenAI (training)

Resources

packagenode-red-contrib-qrusty ↗

homepagehttps://gitlab.com/greeng3/qrusty#readme ↗