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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@open-wa/node-red

v5.0.0-alpha.8

Published

Official @open-wa node-red integration.

Readme

@open-wa/node-red

Official @open-wa node-red integration.

Part of the @open-wa v5 monorepo.

What it does

@open-wa/node-red provides Node-RED nodes for connecting flows to a remote open-wa Easy API session. The package registers three Node-RED node types from package.json: owa-server, cmd, and listen.

Use this integration when Node-RED should call open-wa commands or react to open-wa listener events through a configured Easy API server connection.

Legacy compatibility note: this integration still uses the @open-wa/socket-client surface for backward compatibility, but the active v5 runtime is backed by HTTP RPC + SSE rather than direct Socket.IO. Do not depend on SocketManager from @open-wa/api when integrating with current releases.

Node types

| Node type | Source-visible behavior | | --- | --- | | owa-server | Configuration node that stores name, url, and key, creates a SocketClient, exposes its socket-like connection object, and stores the client in Node-RED global context. It emits and reports connected, disconnected, and connect error status changes. | | cmd | Executes a selected open-wa command against the configured server. It loads command metadata from /meta/basic/commands, accepts method and args from the incoming message or node config, calls server.client.ask(method, args), and supports a timeout in seconds. | | listen | Registers an event listener against the configured server. It loads listener names from /meta/basic/listeners, calls client.listen(listener, listenerFn), sends received event data as msg.payload, and stops the listener on node close. |

Configuration fields

The visible editor templates and runtime source define these fields.

owa-server

  • name: Node-RED display name and status payload socket ID.
  • url: Base URL for the remote open-wa Easy API server.
  • key: Optional API key sent as X-API-Key when loading command and listener metadata and passed to SocketClient.

cmd

  • server: Reference to an owa-server config node.
  • method: Command method to call when the incoming message does not provide msg.method.
  • args: JSON-like command arguments merged with object-like msg.payload values when present.
  • name: Node-RED display name.
  • timeout: Timeout in seconds. The runtime treats -1 as no timeout and falls back to 30 seconds when parsing fails.

listen

  • server: Reference to an owa-server config node.
  • listener: Listener name to register.
  • name: Node-RED display name.

Runtime behavior

  • owa-server constructs new SocketClient(url, key), stores it under the node ID in the global CLIENT_STORE, and removes it on disconnect or node removal.
  • cmd uses /meta/basic/commands to populate command options in the editor. At runtime it prefers msg.method and msg.args, otherwise it parses configured args and msg.payload, then sends the result with client.ask.
  • cmd reports Executing.., Done, timeout, waiting, and missing server states through Node-RED node status.
  • listen uses /meta/basic/listeners to populate listener options in the editor. It registers once per node instance, forwards listener messages as payload, reports connection status, and calls stopListener on close.

Development

  • pnpm --filter @open-wa/node-red add-node
  • pnpm --filter @open-wa/node-red copy
  • pnpm --filter @open-wa/node-red build:editor
  • pnpm --filter @open-wa/node-red build:runtime
  • pnpm --filter @open-wa/node-red build
  • pnpm --filter @open-wa/node-red dev
  • pnpm --filter @open-wa/node-red lint
  • pnpm --filter @open-wa/node-red lint:fix
  • pnpm --filter @open-wa/node-red test
  • pnpm --filter @open-wa/node-red test:watch

Documentation

See the docs site.

License

H-DNH V1.0 - Hippocratic + Do Not Harm