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 🙏

© 2024 – Pkg Stats / Ryan Hefner

redis-ws-alerts

v1.0.8

Published

Alerting clients over express-bound websockets of events posted to redis lists.

Downloads

13

Readme

redis-ws-alerts NPM version Build Status Dependency Status

Alerting clients over express-bound websockets of events posted to redis lists.

Installation

Add redis-ws-alerts to your project (we assume you have pre-installed node.js).

yarn add redis-ws-alerts

How Does It Work?

There's a few things to state up front: This module takes pushed messages from redis lists and forwards them to clients connected over web sockets. Yes, there are some conventions in play, but nothing too burdensome. Of note, publishers of pushed messages must first append to the named list, then push the name of the list onto the tail of the well-known queue specified as the second argument when constructing a connected-content. As well, connected clients must send an 'identify' message to the connection-server with the persistent name of the client. This name serves as the key for the list in redis that holds the messages being forwarded. Queued messages stay queued in the named list until the client with the matching identity connects. Finally, you control the publishing and you control the receiving; utilize a consistent naming scheme and things should work nicely.

With three contexts in play (publishing, popping and dispatching, then receiving), we can set up connected web client alerting with the following:

Popping and Dispatching

import * as express from 'express';
import * as alerter from 'redis-ws-alerts';

const app: express.Application = express();

...

const listen = new alerter.ConnectedContent('redis://localhost:6379', 'watch');
const server = new alerter.ConnectionServer(app, 3001);

listen.onFetch = (key: string, queuedMessage: any) => {
  server.pushNotification(key, queuedMessage);
}

server.onReady = (key: string, isInitial: boolean) => {
  console.log('- ready ' + key + ' ' + isInitial);
};

server.onClose = (key: string, remaining: boolean) => {
  console.log('- close ' + key + ' ' + remaining);
};

process.on("exit", function () {
  server.close();
  listen.close();
});

Publishing

import * as storage from 'redis';

const client = storage.createClient('redis://localhost:6379', {
  retry_strategy: (options: storage.RetryStrategyOptions) => {
    return 10000;
  }
});

...

const customerKey = 'alert/' + customerPoolCode + '-' + customerUniqueCode;

const messageA = {
  message: 'An alert for some customer',
  propX: 'Another property of the message',
  propY: 123,
  recordedOn: new Date(),
};

const messageB = {
  message: 'Another alert for some customer',
  propZ: 456,
  recordedOn: new Date(),
};

client.rpush(customerKey, JSON.stringify({
  event: 'alert',
  ...messageA
}));

client.rpush(customerKey, JSON.stringify({
  event: 'alert',
  ...messageB
}));

client.rpush('watch', customerKey);
client.rpush('watch', customerKey);

Receiving

const socket = new WebSocket('ws://localhost:3001/myapp');

socket.onmessage = (message) => {
  const data = JSON.parse(message.data || '{}');

  if (data.message) {
    console.log('received: ' + data.message);
  }
};

socket.onopen = () => {
  socket.send(JSON.stringify({
    event: 'identify',
    queue: 'alert/' + customerPoolCode + '-' + customerUniqueCode,
  }));
};

License

ISC © Kirk Bulis