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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@alibrate/amqp-client

v1.0.2

Published

Simple connector for amqp protocol

Readme

AMQP client library

High level amqp API written on top of amqplib

Install

npm install

use


const pubsub = require('amqp-client').pubsub;

Publish and Suscribe

Set of functions that implement Publish and Suscribe pattern.

Publishing

The Publisher side looks like this:

const pubsub = require('amqp-client').pubsub;

const msg = {foo: 'bar'};

pubsub.startExchange({url: amqpServerURL, name: 'myexchange'}).then(function (ch) {
	pubsub.publish(ch, 'myfilter', msg);
});

pubsub.startExchange() takes an object with the following properties

  • url : amqp server url. Default: amqp://localhost; often config.amqp.url or context.config.amqp.url
  • name : Name for your exchange, an exchange is like a gateway, so be sure consumers & producers share the same exchange name
  • type : Exchange type. Can be: 'direct', 'topic', 'headers', 'fanout'. See amqplib documentation for more information about all the types. Default: direct
  • options : Options object for internal assertExchange method. See amqplib documentation.

pubsub.publish()

  • ch : the channel returned from startExchange that is used to dispatch messages
  • 'myfilter' : the string filter used for sending messages, consumers must use the same filter to receive
  • msg : the message to pass along to consumers

Suscribers

The Consumer side looks like this:

const pubsub = require('amqp-client').pubsub;

function onMsg(message){
	console.log("Received message:", message);
	let publisherMessage = JSON.parse(message.content);
	console.log("Received content from publisher:", publisherMessage);
}

pubsub.startExchange({url: amqpServerURL, name: 'myexchange'}).then(function (ch) {
	pubsub.consume(ch, 'optional_group', ['myfilter', 'otherFilter'], onMsg);
});

The callback parameter is not the message that was sent from the publisher. Rather it is the actual AMQP message that contains both the stringified version of the message that the producer sent and a whole lot of other information. The actual message sent by the producer is contained in message.content

The consumer open the same exchange myexchange using the same promise startExchange() and then listen for new messages with specific filters. That meeans all the messages sended to myexchange with that filters will be received for this consumer. Note the optional_group parameter. This parameter is used to balance messages between consumers that are using the same group name. That means only one consumer in the same group will receive the message each time like round-robin algorithm. If you use empty string '' as group name then the system will create a random name for you.