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

@rachuta/rabbitmq-wrapper

v0.0.1

Published

A wrapper around amqplib.

Downloads

1

Readme

RabbitMQ Wrapper

This is built on top amqplib which helps your team to write the consumer & publisher faster. This is built thinking in the mind of worker queues pattern.

While creating any queues through the wrapper will automitically create and DLQ & retry.

How to use?

Add this package under the dependencies.

npm install @rachuta/rabbitmq-wrapper --save
// src/index.js

import { Broker } from '@rachuta/rabbitmq-wrapper'

const broker = new Broker()
    .setConfig({
        username: 'username',
        password: 'password',
        hostname: 'hostname',
        port: 5671,
        protocol: 'amqps',
        heartbeat: 20
    })
    .setLogger(winston_loger) // optional; console is the default logger.
    .setConnectionRecoveryTimeout(3000) // optional, value is in MS; default value is 10 seconds
    .build()

// Subscriber
broker.consume('test.queue', function(msg, props, notify) {
    if(!inputValidator(msg))
        notify.reject() // Move message to DLQ

    try {
        // place your code here
    } catch (err) {
        notify.nack() // Move message to delay queue and retry for 3 times with 5 mins interval and move DLQ if unable to process the message in all retries.
    }
 
    notify.ack() // message processed and deleted.
})

// publisher
broker.publish('test.queue', 'Hello World!!', {})

Consumer and publisher functions can take the message as an object/string/buffer. If you pass an object, the message properties are set to application/json, and the message are passed as an object to the consumer.

Publisher can't create queues so, we recommend to deploying consumers before publishers.

Message retry mechanism

@rachuta/rabbitmq-wrapper enables message retry mechanism by default, and there is no way to disable it. So please set the below headers to configure the retry mechanism.

broker.consume('notification.t.sms', handler , {
    messageTtl: 60000, // message live in queue before move to DLQ; default value is 5 min
    headers: {
        'x-max-retry': 4, // maximum message retries; default value is 3
        'x-delay': 30000 // each retry delay; default value is is 5 min
    }
})

P.S: Only nack messages will be retried.

How to run test locally?

You need Docker to run RabbitMQ Install.

# Terminal 1
$ docker run -it --rm --name rabbitmq -p 5672:5672 -p 15672:15672 rabbitmq:latest

# Terminal 2(code base)
$ npm run test