Skip to content
An asynchronous messaging library, written in JavaScript, for node and the web browser
JavaScript HTML
Branch: master
Clone or download
KrisSiegel 7.0.0 (#70)
* Update travis for new node version testing
Version 7.0.0 setup

* Added package-lock
Updated some npm modules due to npm audit report
Removed msngr.asyncify()

* Build updates

* Reverted grunt minor update as the minor update updates many dependencies that are major and breaking in super old versions of node.
Revert npm audit fixes; they are just build dependencies and I went through them they are of no concern in our usage.

* Cleaned up tiny bit more code
Increased timeout on one weird test case (long explanation but it's fine for now)
Added clean option to grunt / npm scripts

* Minor tweaks

* Update changelog notes
Latest commit c173dd2 Jan 11, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
resources 5.2.1 (#65) Jun 16, 2017
src 7.0.0 (#70) Jan 11, 2019
test 6.0.0 (#66) Jul 28, 2017
.gitignore 5.1.0 (#62) Dec 12, 2016
.npmignore 7.0.0 (#70) Jan 11, 2019
.travis.yml 7.0.0 (#70) Jan 11, 2019 7.0.0 (#70) Jan 11, 2019
Gruntfile.js 7.0.0 (#70) Jan 11, 2019
LICENSE 7.0.0 (#70) Jan 11, 2019 Making sure Kris doesn't fall behind. Big, important update here. (#69) Jan 8, 2019
bower.json 7.0.0 (#70) Jan 11, 2019
msngr.js 7.0.0 (#70) Jan 11, 2019
msngr.min.js 7.0.0 (#70) Jan 11, 2019
package-lock.json 7.0.0 (#70) Jan 11, 2019
package.json 7.0.0 (#70) Jan 11, 2019

msngr.js logo

Messaging is a powerful development pattern that makes decoupling components and providing internal APIs incredibly easy. The primary goal of msngr is to provide a high quality, asynchronous method of consuming and emitting messages that work in both node and the web browser.

Snag a copy of msngr

Install via npm or bower by running npm install msngr or bower install msngr

Grab a copy of the msngr.js or msngr.min.js files directly from this repo

Reference msngr directly from cdnjs

Hello, World!

// I can call a function when I receive a specific message!
msngr("Output").on((words) => {
    console.log(words); // Outputs 'Hello, World!', 'I'm chainable!' and 'Weee'
    return 42;

// I can emit messages of any type and I can chain them together.
  .emit("Hello, World!")
  .emit("I'm chainable!")
// I can notify and even return values when a message is finished being processed
    .emit("Processing", (results) => {
        console.log(results); // Prints [42]
// Even better, I can return a result asynchronously!
    .on((input, message, async) => {
        const done = async();
  .emit("Processing", (results) => {
        console.log(results); // Also prints [42]

// I can emit and persist a message so future handlers can receive it
msngr("Important", "Message").persist("I am persisted!");

// See?
msngr("Important", "Message").on((text) => {
    console.log(text); // Outputs 'I am persisted!'
  // Then I can remove the persisted data once I'm done with it
    msngr("Important", "Message").cease();

// I can even guarantee a handler is called only once
msngr("Once").once((str) => {
    console.log(str); // Only outputs 'Just once'

msngr("Once").emit("Just once").emit("asdljadlka").emit("sadjkhada");

// Did I mention I'm completely asynchronous?
    .on((text) => {
  .emit("This is async text");
console.log("This is sync text"); // This will print before everything in this example

Anatomy of a message

Messages can be comprised of a topic, category and subcategory with topic being the only required piece all of which are specified in the main msngr function msngr(topic, category, subcategory). This allows for a large range of message consumption from the very general to the highly specific.

Consuming and emitting

When consuming or emitting a message you can choose to match just the topic, the topic and category or the topic, category and subcategory. This allows for a great amount of specificity when choosing what your handler can take care of (is it generic in that it can handle anything? should it only handle specific categories? subcategories?). Take a look at this example:

// Handler that receives all profile save attempts
msngr("Profile", "Save").on((payload) => {

// Handler that only received profile saves in json
msngr("Profile", "Save", "application/json").on((payload) => {
    console.log("Save the json payload");

// Handler that only received profile saves in xml
msngr("Profile", "Save", "application/xml").on((payload) => {
    console.log("Save the xml payload");

msngr("Profile", "Save", "application/json").emit({ name: "myname!" });
msngr("Profile", "Save", "application/xml").emit("<xml><name>myname!</name></xml>");

The example above demonstrates that the handler will only fire when the specified criteria of a registered on handler is satisfied.


A mechanism for middleware exists that creates a global or localized affect. This allows for payload transformation to occur prior to any messages and their payloads being delivered to handlers. A middleware needs to be registered via msngr.middleware(key, fn, force) where the key is the name of the middleware, the fn is the middleware itself and force is a boolean that specifies whether the middleware should execute on all messages or not (if false then msngr().use(key) needs to be called on a message to have it applied).

msngr.middleware("uppercase", (payload, message) => {
    if ( {
        return payload.toUpperCase();
    return payload;
}, true);

msngr("SayIt").on((payload) => {
    console.log(payload); // Prints 'HELLO, WORLD!'

msngr("SayIt").emit("hello, world!");

Persist, once and drop

Messages can also have a payload that is persistent. This is incredibly handy when doing initialization. You can specify a message when something is initialized and persist the message (even with an empty payload) so that handlers registered before or after said initialization are still called. This is done through msngr().persist() and can be ended through msngr().cease().

There is also a msngr().once() that works just like msngr().on() except it is guaranteed to execute only once. In a similar vein you can drop msngr().on() registered handles either one at a time through msngr().drop(fn) or all at once for a specific message via msngr().dropAll().

Validation is a very important part of dealing with a dynamic language such as JavaScript. The function is an attempt to make it as intuitive and straight-forward as possible. Simply call providing whatever you want to check as the parameter (you can also pass in multiple parameters to check them all in an AND fashion) then call one of the following properties on the returned object:; // checks for arguments object; // checks for boolean; // check for string; // checks for date; // checks for array; // checks for number; // checks for object; // checks for function; // checks for symbol; // checks to see if the obj exists; // checks to see if an object, array or string is empty (including null and undefined); // checks to see if it's an HTML Element; // checks to see if it's an HTML NodeList


So if you want to create an asynchronous process many developers turn to setTimeout(fn, 0); but that's actually rather slow to execute in web browsers (typically values less than 10ms or so are ignored and even 0ms isn't guaranteed to execute immediately). Using setImmediate(fn) is a far better choice but it's almost exclusively available in node and IE. This is where msngr.immediate(fn) comes in. There is a way to simulate setImmediate(fn) when it doesn't exist in a web browser so msngr.immediate(fn) will use whatever the fastest solution that exists on the platform it is running on to execute something asynchronously.

msngr.immediate(() => {
    console.log("Hey there!");

msngr.parallel(methods, callback) / msngr.series(methods, callback)

Handling asynchronous behaviors can be difficult and there are many libraries (async.js) and techniques (promises, async & await) for handling such issues. But sometimes you just need a simple way to take multiple methods and combine them. Msngr uses this capability internally for handling message delegation and processing of middleware so these two methods are the public version of the very same API.

const props = { };
    () => { props.value1 = 42; },
    () => { props.value2 = "forty two"; },
    () => { props.value3 = true; },
], () => {
    console.log(props.value1); // Prints 42
    console.log(props.value2); // Prints 'forty two'
    console.log(props.value3); // Prints true

    () => { return "s" },
    () => { return "e" },
    (async) => { async()("r") },
    (async) => { async()("i") },
    (async) => { async()("e") },
    () => { return "s" }
], (results) => {
    console.log(results.join("")); // Prints "series"


For questions, news, and whatever else that doesn't fit in GitHub issues you can follow me @KrisSiegel

Copyright © 2014-2019 Kris Siegel

You can’t perform that action at this time.