Security News
PyPI Introduces Digital Attestations to Strengthen Python Package Security
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
ts-event-bus
Advanced tools
[!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.
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;
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")],
});
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'
...
}
})
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();
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 }),
};
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 }),
};
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;
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);
};
}
}
FAQs
Distributed messaging in Typescript
The npm package ts-event-bus receives a total of 1,096 weekly downloads. As such, ts-event-bus popularity was classified as popular.
We found that ts-event-bus demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 6 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.