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

msg-channel-js

v1.0.0

Published

Sequencing async processing for messages

Downloads

4

Readme

channel-js - Sequencing async message processing

This is inspired by Go channels.

Channels allows separating the code for sending messages from the code for processing messages.

Messages are processed in the order they arrive. Each message is fully processed before the next message is picked up, even if the handler has async calls, resulting in sequential message processing.

The sender does not wait for the message to be processed (the sending is fire-and-forget).

The typical scenario

The web page begins to send user analytics events as soon as loaded, but the analytics library requires some delay to be properly initialized, so the events need to be queued.

Processing of a single event involves modifying some internal data structures, and having 2 events being processed at a time can lead to race condition due to async calls, so you want to process them in sequence.

Usage

Import:

const { makeChannel } = require('msg-channel-js');

Basic usage:

const ch = makeChannel();
ch.attachHandler(async msg => { console.log(msg.id); });
ch.write({ id: 1 });

You can write messages to the channel as soon as you create it, in that case they will be queued until you attach the handler:

const ch = makeChannel();
ch.write({ id: 1 });
ch.attachHandler(async msg => { console.log(msg.id); });

This becomes truly useful when the handler is an async function, but you still want to make sure you completely processed one message before you start processing the next one.

Example:

const msg1 = { id: 1 };
const msg2 = { id: 2 };
const msg3 = { id: 3 };

const delay = (delayInms) => {
    return new Promise(resolve => setTimeout(resolve, delayInms));
}

const handler = async msg => {
    console.log(`START ${msg.id}`);
    await delay(100);
    console.log(`MID ${msg.id}`);
    await delay(100);
    console.log(`FINISH ${msg.id}`);
}

const ch = makeChannel();

// no handler attached -> the messages will be queued
// you don't wait for messages to be processed
ch.write(msg1);
ch.write(msg2);

// here the processing starts
ch.attachHandler(handler);

// meanwhile, you can queue more messages
ch.write(msg3);

// prints:
// START 1
// MID 1
// FINISH 1
// START 2
// MID 2
// FINISH 2
// START 3
// MID 3
// FINISH 3