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

mqemitter

v6.0.2

Published

An Opinionated Message Queue with an emitter-style API

Downloads

719,561

Readme

MQEmitter

ci Known Vulnerabilities js-standard-style
Dependencies Status devDependencies Status
NPM version NPM downloads

An Opinionated Message Queue with an emitter-style API, but with callbacks.

If you need a multi process MQEmitter, check out the table below:

Installation

npm install mqemitter

Examples

const mq = require('mqemitter')
const emitter = mq({ concurrency: 5 })
const message

emitter.on('hello world', function (message, cb) {
  // call callback when you are done
  // do not pass any errors, the emitter cannot handle it.
  cb()
})

// topic is mandatory
message = { topic: 'hello world', payload: 'or any other fields' }
emitter.emit(message, function () {
  // emitter will never return an error
})

API

new MQEmitter ([options])

  • options <object>
    • concurrency <number> maximum number of concurrent messages that can be on concurrent delivery. Default: 0
    • wildcardOne <string> a char to use for matching exactly one non-empty level word. Default: +
    • wildcardSome <string> a char to use for matching multiple level wildcards. Default: #`
    • matchEmptyLevels <boolean> If true then wildcardOne also matches an empty word. Default: true
    • separator <string> a separator character to use for separating words. Default: /

Create a new MQEmitter class.

MQEmitter is the class and function exposed by this module. It can be created by MQEmitter() or using new MQEmitter().

For more information on wildcards, see this explanation or Qlobber.

emitter.emit (message, callback)

  • message <object>
  • callback <Function> (error) => void
    • error <Error> | null

Emit the given message, which must have a topic property, which can contain wildcards as defined on creation.

emitter.on (topic, listener, [callback])

  • topic <string>
  • listener <Function> (message, done) => void
  • callback <Function> () => void

Add the given listener to the passed topic. Topic can contain wildcards, as defined on creation.

The listener must never error and done must not be called with an err object.

callback will be called when the event subscribe is done correctly.

emitter.removeListener (topic, listener, [callback])

The inverse of on.

emitter.close (callback)

  • callback <Function> () => void

Close the given emitter. After, all writes will return an error.

Wildcards

MQEmitter supports the use of wildcards: every topic is splitted according to separator.

The wildcard character + matches exactly non-empty one word:

const mq = require('mqemitter')
const emitter = mq()

emitter.on('hello/+/world', function(message, cb) {
  // will ONLY capture { topic: 'hello/my/world', 'something': 'more' }
  console.log(message)
  cb()
})
emitter.on('hello/+', function(message, cb) {
  // will not be called
  console.log(message)
  cb()
})

emitter.emit({ topic: 'hello/my/world', something: 'more' })
emitter.emit({ topic: 'hello//world', something: 'more' })

The wildcard character + matches one word:

const mq = require('mqemitter')
const emitter = mq({ matchEmptyLevels: true })

emitter.on('hello/+/world', function(message, cb) {
  // will capture { topic: 'hello/my/world', 'something': 'more' }
  // and capture { topic: 'hello//world', 'something': 'more' }
  console.log(message)
  cb()
})

emitter.on('hello/+', function(message, cb) {
  // will not be called
  console.log(message)
  cb()
})

emitter.emit({ topic: 'hello/my/world', something: 'more' })
emitter.emit({ topic: 'hello//world', something: 'more' })

The wildcard character # matches zero or more words:

const mq = require('mqemitter')
const emitter = mq()

emitter.on('hello/#', function(message, cb) {
  // this will print { topic: 'hello/my/world', 'something': 'more' }
  console.log(message)
  cb()
})

emitter.on('#', function(message, cb) {
  // this will print { topic: 'hello/my/world', 'something': 'more' }
  console.log(message)
  cb()
})

emitter.on('hello/my/world/#', function(message, cb) {
  // this will print { topic: 'hello/my/world', 'something': 'more' }
  console.log(message)
  cb()
})

emitter.emit({ topic: 'hello/my/world', something: 'more' })

Of course, you can mix # and + in the same subscription.

LICENSE

MIT