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

midnight-bus-explorer

v0.0.2

Published

Terminal tool for operation on azure service busses

Downloads

4

Readme

Midnight Bus Explorer

Terminal tool for adminstration and maintenance of Azure Service Buses

Install

$ npm install midnight-bus-explorer -g

Install local dev

In the project root directory run the following to install globally

$ npm install -g p

Configure

Before you can use Midnight Bus Explorer you need to configure your connection strings. The configure takes a name and a azure service bus connections string and will save it to a config file in your home folder.

Ex: $ midnightbus configure myazb "Endpoint=sb://myazb.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=notARealkey"

Once you have an environment configured you can now start using the utility of Midnight bus explorer.

If you forget what configs you have or have set up use the listConfig call to see whats configured in the settings.

Usage

ListQueues:

This action will give you a list of the queues in your service bus.

ex : $ midnightbus myazb ListQueues

Options

  • showQueueCounts (true/false): takes true or false and will toggle showing number of messages in the active and dead letter queue. Default is false.

monitor:

This action allows you to monitor you queues in the terminal similar top in unix.

ex: $ midnightbus myazb monitor

Options

  • refresh(number): specify how frequently in seconds to refresh the display of queue information, default is two seconds.

peekQueue:

This action allows you to peek at whats in a particular queues subqueues, such as the active queue or the dead letter queue.

required

You must provide the name of the queue you want to peek into

ex: $ midnightbus myazb peekQueue name-of-queue-to-peek

Options

  • numberOfMessages: (number) takes how many messages to peek, default is 10.
  • messagesFromIndex (number): where to start from in the sub queue index, default is 0.
  • submessageQueue (number): Sub queue you wish to peek at, default is "deadLetter".
  • outputToFile (filePath): if provided with a filepath Will write subqueue contents to a specified file.
  • formatForResend (true/false): Will attempt to format file output in a way consumable by the sendMessages.
  • filterSubject(string): will do simple pattern matching on the subject of a message in the sub queue and will only return messages that contain the provided filter string.

sendMessages:

Will send messages from a provided json file to a queue.

required

You must append the action with the bus you are sending too and the path to the json file containing the messages you are sending

EX: $ midnightBus sendMessages name-of-queue-to-send-stuff ./myData/someData.json

Below is how the program expects you json file to be set up with the messages you are sending

{
  "messages": [
    {
      "commandSubject": "DoTheThing+Command",
      "commandBody": {
        "someKindOfId": ";lkjhsdoidsjoijdfadsoijf",
        "somethingElse": "herpDerp",
        "someNumbersToo": 46546546549687464
      }
    }
  ]
}