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

ts-event-bus

v4.2.0

Published

Distributed messaging in Typescript

Downloads

14,067

Readme

ts-event-bus

by Dashlane

Build Status Dependency Status

[!CAUTION] This package is no longer maintained. It is strongly advised against using it in any new project.

Distributed messaging in Typescript

ts-event-bus is a lightweight distributed messaging system. It allows several modules, potentially distributed over different runtime spaces to communicate through typed messages.

Getting started

Declare your events

Using ts-event-bus starts with the declaration of the interface that your components share:

// MyEvents.ts
import { slot, Slot } from "ts-event-bus";

const MyEvents = {
  sayHello: slot<string>(),
  getTime: slot<null, string>(),
  multiply: slot<{ a: number; b: number }, number>(),
  ping: slot<void>(),
};

export default MyEvents;

Create EventBus

Your components will then instantiate an event bus based on this declaration, using whatever channel they may want to communicate on. If you specify no Channel, it means that you will exchange events in the same memory space.

For instance, one could connect two node processes over WebSocket:

// firstModule.EventBus.ts
import { createEventBus } from "ts-event-bus";
import MyEvents from "./MyEvents.ts";
import MyBasicWebSocketClientChannel from "./MyBasicWebSocketClientChannel.ts";

const EventBus = createEventBus({
  events: MyEvents,
  channels: [new MyBasicWebSocketClientChannel("ws://your_host")],
});

export default EventBus;
// secondModule.EventBus.ts
import { createEventBus } from "ts-event-bus";
import MyEvents from "./MyEvents.ts";
import MyBasicWebSocketServerChannel from "./MyBasicWebSocketServerChannel.ts";

const EventBus = createEventBus({
  events: MyEvents,
  channels: [new MyBasicWebSocketServerChannel("ws://your_host")],
});

Usage

Once connected, the clients can start by using the slots on the event bus

// firstModule.ts
import EventBus from './firstModule.EventBus.ts'

// Slots can be called with a parameter, here 'michel'
EventBus.say('michel', 'Hello')

// Or one can rely on the default parameter: here DEFAULT_PARAMETER
// is implicitely used.
EventBus.say('Hello')

// Triggering an event always returns a promise
EventBus.say('michel', 'Hello').then(() => {
    ...
})

EventBus.getTime().then((time) => {
    ...
})

EventBus.multiply({a: 2, b: 5 }).then((result) => {
    ...
})

EventBus.ping()
// secondModule.ts
import EventBus from "./secondModule.EventBus.ts";

// Add a listener on the default parameter
EventBus.ping.on(() => {
  console.log("pong");
});

// Or listen to a specific parameter
EventBus.say.on("michel", (words) => {
  console.log("michel said", words);
});

// Event subscribers can respond to the event synchronously (by returning a value)
EventBus.getTime.on(() => new Date().toString);

// Or asynchronously (by returning a Promise that resolves with the value).
EventBus.multiply.on(
  ({ a, b }) =>
    new Promise((resolve, reject) => {
      AsynchronousMultiplier(a, b, (err, result) => {
        if (err) {
          return reject(err);
        }
        resolve(result);
      });
    })
);

Calls and subscriptions on slots are typechecked

EventBus.multiply({a: 1, c: 2}) // Compile error: property 'c' does not exist on type {a: number, b: number}

EventBus.multiply.on(({a, b}) => {
    if (a.length > 2) { // Compile error: property 'length' does not exist on type 'number'
        ...
    }
})

Lazy callbacks

Slots expose a lazy method that will allow you to call a "connect" callback when a first client connects to the slot, and a "disconnect" callback when the last client disconnect.

Remote or local clients are considered equally. If a client was already connected to the slot at the time when lazy is called, the "connect" callback is called immediately.

const connect = (param) => {
  console.log(
    `Someone somewhere has begun listening to the slot with .on on ${param}.`
  );
};

const disconnect = (param) => {
  console.log(`No one is listening to the slot anymore on ${param}.`);
};

const disconnectLazy = EventBus.ping.lazy(connect, disconnect);

const unsubscribe = EventBus.ping().on(() => {});
// console output: 'Someone somewhere has begun listening to the slot with .on on $_DEFAULT_$.'

unsubscribe();
// console output: 'No one is listening to the slot anymore on $_DEFAULT_$.'

const unsubscribe = EventBus.ping().on("parameter", () => {});
// console output: 'Someone somewhere has begun listening to the slot with .on on parameter.'

unsubscribe();
// console output: 'No one is listening to the slot anymore on parameter.'

// Remove the callbacks.
// "disconnect" is called one last time if there were subscribers left on the slot.
disconnectLazy();

Buffering

When the eventBus is created with channels, slots will wait for all transports to have registered callbacks before triggering.

This buffering mechanism can be disabled at the slot level with the noBuffer config option:

const MyEvents = {
  willWait: slot<string>(),
  wontWait: slot<string>({ noBuffer: true }),
};

Auto-reconnection

In order to re-establish a lost connection when triggering an event a Channel needs to implement the autoReconnect method. See example: RuntimeConnect It's also possible to fine tune and deactivate this feature on a per-slot basis :

const MyEvents = {
  willAutoReconnect: slot<string>(),
  wontNotAutoReconnect: slot<string>({ autoReconnect: false }),
};

Syntactic sugar

You can combine events from different sources.

import { combineEvents } from "ts-event-bus";
import MyEvents from "./MyEvents.ts";
import MyOtherEvents from "./MyOtherEvents.ts";

const MyCombinedEvents = combineEvents(MyEvents, MyOtherEvents);

export default MyCombinedEvents;

Using and Implementing Channels

ts-event-bus comes with an abstract class GenericChannel. To implement your own channel create a new class extending GenericChannel, and call the method given by the abstract class: _connected(), _disconnected(), _error(e: Error) and _messageReceived(data: any).

Basic WebSocket Channel example:

import { GenericChannel } from "ts-event-bus";

export class MyBasicWebSocketChannel extends GenericChannel {
  private _ws: WebSocket | null = null;
  private _host: string;

  constructor(host: string) {
    super();
    this._host = host;
    this._init();
  }

  private _init(): void {
    const ws = new WebSocket(this._host);

    ws.onopen = (e: Event) => {
      this._connected();
      this._ws = ws;
    };

    ws.onerror = (e: Event) => {
      this._ws = null;
      this._error(e);
      this._disconnected();
      setTimeout(() => {
        this._init();
      }, 2000);
    };

    ws.onclose = (e: CloseEvent) => {
      if (ws === this._ws) {
        this._ws = null;
        this._disconnected();
        this._init();
      }
    };

    ws.onmessage = (e: MessageEvent) => {
      this._messageReceived(e.data);
    };
  }
}

Examples