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

props-lib-mq

v0.0.1

Published

Handling lib-mq operations

Downloads

1

Readme

lib-mq

Connect to RabbitMQ in order to publish / consume messages.

The library is wrapping amqp.node client library

Connecting to Rabbit

The following will open a connection with rabbit so later publishing and consuming will be possible. Since we would like to have one single connection per running node it's best to add this to server.start in app.js The connect function already wrapping a retry mechanism in case the connection fails.

import { MQClient } from 'props-lib-mq';

MQClient.connect( RABBIT_URL );

Publishing to Rabbit

publish function signature

static async publish(exchangeName, exchangeType, key, data, correlationId = null, opts = {}):Promise<boolean>
import { MQClient } from 'props-lib-mq';

const published =  MQClient.publish('user', 'topic', 'event.success.user.join.room', { user_id: "123", room_id: "123" }).then(published => {
  if(published) console.log('Woot Woot');
  else console.error('Publish Failed');
}).catch(err){
  // Critical error
};

Consuming from rabbit

When consuming we need first to wait for a connection to be available, once that happen a 'ready' event will be emitted. The event will be emitted on each reconnection made to rabbit in case the connection was suddenly closed and had to reconnect those promising continues consuming subsequent an event of connection close / error.

consume function signature

static consume(exchangeName, exchangeType, key, queueName, opts = {}, callback)
import { MQClient, MQClientEvents } from 'props-lib-mq';

MQClientEvents.on('ready', () => {
  MQClient.consume('user', 'topic', 'event.success.user.offline', 'room-event-success-user-offline', {}, (data, ack, nack, rawMsg) => {
    
    // Handle message here
    
  });
});