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

node-rabbit-viewer

v1.0.8

Published

Viewer for node-rabbit-connector documentation

Readme

Travis (.org) master npm Docker Automated build Docker Pulls

node-rabbit-viewer

ATTENTION: This module is currently in alpha development phase

This is a small webapp that enables exploring RabbitMQ configuration of consumers and requesters, because this can get very messy sometimes. This module was written for the related npm module node-rabbit-connector.

Install

Using npm:

npm install --save node-rabbit-viewer

Using yarn:

yarn add node-rabbit-viewer

Usage

Start

// create a script in your package.json, where viewer path is the path to the viewer config json
"startRabbitViewer": "VIEWER_PATH=./path/to/rabbitmq.json node node_modules/node-rabbit-viewer/dist/index.js"

or

// start with docker image
docker run -d -v path/to/config/folder:/usr/rabbitViewer/config -e VIEWER_PATH=./config/rabbitmq.json -e VIEWER_PORT=8888 -p 8880:8888 ebuccaneer/node-rabbit-viewer

Webapp

Starting on http://localhost:8880 per default.

Example

Here is an example of the rabbitmq.json viewer config. Also an example here

{
  "services": {
    "someService": { // name of the service
      "requests": {
        "work": [ // array for work requests
          {
            "queue": "someName1", // name of the queue to send to (must be unique, also regarding rpc names)
            "message": { // the sent message format, either one of msg/data or both
              "msg": {  // the message property
                "description": "Some important message"
              },
              "data": { // the data section
                "someProperty": { // property name
                  "$ref": "Object", // reference to a defined model
                  "required": false
                }
              }
            }
          }
        ],
        "rpc": [  // array of rpc calls
          {
            "name": "someName2", // name of the queue to send to (must be unique, also regarding work queue names)
            "highPriority": false,
            "message": {
              "data": {
                "someProperty": {
                  "type": "string", // property type
                  "description": "Some string property",
                  "required": false
                }
              }
            }
          }
        ],
        "topic": [  // array of topic messages
          {
            "exchange": "someExchange", // exchange to send to
            "key": "some.key",  // routing key of message
            "durable": true,  // indicates if exchange will survive broker restarts
            "message": {
              // like shown before
            }
          }
        ]
      },
      "consumes": {
        "work": [ // array of work consumers
          {
            "queue": "someName1",
            "noAck": false,   // indicates if receiving of messages has to be acknowledged
            "message": {
              // like shown before
            },
            "task": "This then does some task with received message"  // small description of what is done on message reception
          }
        ],
        "rpc": [  // array of rpc call listeners
          {
            "name": "someName2",
            "highPriority": false,
            "message": {
              // like shown before
            },
            "task": "This then does some task with received message"
          }
        ],
        "topic": [  // array of topic message consumers
          {
            "exchange": "someExchange",
            "key": "some.*",
            "durable": true,
            "message": {
              // like shown before
            },
            "task": "This then does some task with received message"
          }
        ]
      },
      "excepts": {  // this is for revoking binding something of "all" section to this service
        "requests":{
          "work": [
            "logs"  // one or more names of work queues
          ],
          "rpc": [
            "someName"  // one or more rpc names
          ],
          "topic": [
            { // object with exchange and key of topic
              "exchange": "someExchange",
              "key": "some.key"
            }
          ]
        },
        "consumes":{
          // same format as with requests
        }
      }
    }
  },

  "all": {  // defining a request or consumer that is done by all specified services
    // same format as in a single service definition
  },

  "models": { // section for defining models to use in property definitions
    "Object": { // name of the model
      "type": "object",
      "description": "This object is used to pass log messages to the logger MS",
      "properties": { // properties of a model
        "msg": {
          "type": "string",
          "description": "This is an error message",
          "required": false
        }
      }
    }
  }
}