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

rabbit-rr

v2.0.0

Published

Simple rabbitmq client for use with REQ/REP pattern

Downloads

5

Readme

rabbit-rr

build statusCoverage Status

A simple rabbitmq module based on amqplib and inspired by rabbit.js meant to provide a simple callback interface for using a req/rep pattern. This is ideal when doing concurrent operations that require the return callback to be properly associated with the data that was sent (and the result then returned)

Goal:

The purpose of this module is to hide all of the dirty async startup needed when connecting to rabbit. When initializing a constructor, we establish a connection to rabbit and begin creating a channel WITH that connection. This channel and connection is used with any socket created with the rabbit instance. We take care of deferring the function calls of connect and send (send is only for the REQ socket) so that you have a clean and simple API to use. Each Rabbit and Socket instance is an EventEmitter with various events associated for gaining insight into the inner workings. The main event to worry about though is the message event on the REP socket which emits any message received from a REQ socket with a callback to reply to it. Please see the example below to understand my ramblings.

Example:

Below shows a simple use case


var Rabbit = require('rabbit-rr');

//
// Remark: This constructor accepts an object or URL string with the
// options you want to pass into `amqplib` to connect (e.g ssl options)
//
var rabbit = new Rabbit()
  .on('ready', function () {
    console.log('We are conected to Rabbit!');
  });

//
// Creates a socket to handle sending requests to Rabbit,
// options are accepted as a second argument
//
var req = rabbit.socket('REQ')
  .on('error', console.error.bind(console))
  .on('ready', function () {
    // Called when channel has been assigned
    console.log('REQ socket Ready!');
  })
  // Connect to the specified Queue, accepts an optional callback
  .connect('made_up_queue')
  .on('connect', function () {
    console.log('REQ has connected to queue');
  })
  // We assume and parse payloads as objects
  .send({ foo: 'bar' }, function (err, msg) {
    if (err) return console.error('application error from REP socket %s', err.message)
    console.log('received msg %j', msg);
  });

var rep = rabbit.socket('REP')
  .on('error', console.error.bind(console))
  .on('ready', function () {

    console.log('REP socket ready');
  })
  .connect('made_up_queue')
  .on('connect', function () {
    console.log('REP has connected');
  })
  // Listen for messages from requester
  .on('message', function (msg, reply) {
    // Reply to them with a particular payload
    // We assume object payloads everywhere
    reply(undefined, { reply: 'wooo' });
  });