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

messageq

v0.3.1

Published

A reliable delivery pub/sub messaging system.

Downloads

2

Readme

messageq Build Status

A simple pub/sub system that uses reliable task queues for delivery. It uses relyq (simple Redis-backed reliable task queues) to establish reliable messaging. It also provides a pub/sub interface for reliable messaging by adding a discovery service backed by any database or service using a modular system.

Operation

Install:

npm install messageq

Usage:

var redis = require('redis'),
  cli = redis.createClient();

var messageq = require('messageq'),
  mq = new messageq.RedisMQ(cli, {prefix: 'my-endpoint', discovery_prefix: 'my-queue-system'}); // see options below

mq.subscribe('channel-name' [, function (message) {...}]);
mq.on('message:channel-name', function (message) {...});

mq.publish('channel-name', {my: 'message'}, function (err) {...});

Options:

Note that all options can be passed in at create time. Some, which apply to subscriptions only, can be overridden or set at subscribe time.

  • prefix: 'my-endpoint' (required) - The redis key prefix for the sub-queues.

  • delimeter: '|' (default: ':') - The redis key delimeter for the sub-queues and discovery prefix if using RedisMQ.

  • idfield: 'tid' (default: 'id') - The field of the task objects where the ID can be found.

  • ensureid: false (default: true) - Adds an ID to the object if not there.

  • ttl: 5000 (default: 5s (in ms)) - Time between subscriber lookups

  • Q: relyq.RedisJsonQ (defaults to RedisJsonQ) A relyq type to use as the sub-queues backend. Each one has specific options (overridable at subscribe time) that you should check out before continuing.

These options can be overridden at subscribe time:

  • max_out: 10 (default: 0/infinity) Max number of message events to fire concurrently.
  • clean_finish: true (default: true) Does not keep successfully finished messages. Set to 'keep_storage' if you wish to keep them in storage but still remove from the queue.

In addition, the Discovery Backends have their own options (see below).

Tests

npm install -g nodeunit
npm test

Discovery Backends

The messageq system can use any of the following backends, which are subclasses of the master type, so each represents a fully functional messageq system type.

Redis

The Redis backend is the primary suggested one, because of its proximity to the queues.

mq = new messageq.RedisMQ(cli, options);

Options:

  • discovery_prefix: 'my-queue-system' (required) - The redis key prefix for the discovery backend

License

See LICENSE file.