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

node-red-contrib-dyno-websocket

v0.11.4

Published

WebSocket with dynamic configuration that can be changed in runtime

Readme

red-contrib-dyno-websocket

NPM Version

Dynamic WebSocket client node for Node-RED.

Source code is published at Codeberg

Install

npm install node-red-contrib-dyno-websocket

Node

  • Type: dyno-websocket
  • Inputs: 1
  • Outputs: 2 (data, control)

Configuration:

  • url: string, can be wss:// or ws:// schema
  • headers: object?: optional, http headers to send during upgrade
  • topic: string?: optional, given topic will be added to all outgoing msg
  • autoConnect: boolean?: when true, node attempts connection on deploy and relevant config updates

These are startup defaults and can be changed at runtime with commands.

Input Commands

Set msg.command to one of:

  • config-set: overwrite configuration of node. Configuration should be sent in msg.payload. If url or headers are sent while connected, connection will be re-opened with new settings. If disconnected and autoConnect is true, node will attempt to connect.
    • url: string
    • headers: object?
    • topic: string?
    • autoConnect: boolean?
  • config-get: return current configuration in msg.payload
  • config-reset: reset dynamic configuration to values set in node editor
  • counters: return current runtime counters in msg.payload
  • counters-reset: reset runtime counters and return updated values in msg.payload
  • connect
  • disconnect
  • reconnect

If msg.command is not set, msg.payload is sent to the socket:

  • Buffer/Uint8Array: sent as binary frame
  • object: sent as JSON serialized string
  • others: sent as String(payload)

Outputs

Data output (output 1):

  • binary frame: raw Buffer
  • non-binary frame: parsed as JSON with fallback to plain-text

Control output (output 2):

  • Success:

    { topic?, event: string, ok: true, payload: any, counters: object }
  • Failure:

    {
      topic?,
      event: string,
      ok: false,
      payload: { message: string, error: string, extra?: any },
      counters: object
    }

Persistence

Node state is stored in node context (config, state) and can be inspected on Context Data page.

Note: settings will be lost after node re-deployment if Node-RED contextStorage is not set. Make sure you have at least one storage enabled, memory for example:

  // add to settings.js in you node-red home folder
  contextStorage: {
    default: { module: "memory" },
  },