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

@trutoo/event-bus

v2.3.0

Published

Typesafe cross-platform pubsub event bus ensuring reliable communication between fragments and micro frontends.

Downloads

11,327

Readme

Event Bus

Continuous Delivery Coverage Status GitHub release (latest by date) [npm downloads] npm bundle size License

Simple typesafe cross-platform pubsub communication between different single page applications, web components, fragments, or services. Purposefully built for a micro frontend architecture with a distributed responsibility for deployment. Allowing for framework agnostic and safe communication between different implementations and version. Catch those pesky event errors early :heart:.


Table of Contents


Purpose

This project was created to improve upon some of the deficits CustomEvents has in relation to event communication between separate web components or fragments, which often is the preferred way of communication. Below points are some of the benefits of using this pub-sub solution over the native solution.

  1. Each fragment can register on a custom named event channel with an optional JSON schema draft-04 to ensure all future traffic on that channel follows the specification. This means incompatibilities are reported before any payload is sent and every payload will be typesafe.

  2. The individual event channels stores the last payload allowing new fragments or asynchronous subscriptions to ask for a replay of the last payloads data as a first callback.

  3. CustomEvents require a polyfill to work in older browsers, while this project works out of the box with Internet Explorer 11.

Installation

Install the package from the npm registry @trutoo/event-bus as a production/runtime dependency.

npm install @trutoo/event-bus

or

yarn add @trutoo/event-bus

Note: dropped publishing to GitHub packages to simplify releases.

Then either import the side effects only exposing a eventBus global instance.

import '@trutoo/event-bus';
// or
require('@trutoo/event-bus');

eventBus.register(/*...*/);

or import the EventBus class to create your own instance.

import { EventBus } from '@trutoo/event-bus';
// or
const { EventBus } = require('@trutoo/event-bus');

const myEventBus = new EventBus();
myEventBus.register(/*...*/);

or using the UMD module and instance.

<script src="https://unpkg.com/@trutoo/event-bus@latest/dist/index.umd.min.js"></script>
<script>
  eventBus.register(/*...*/);
  // or
  const myEventBus = new EventBus.EventBus();
  myEventBus.register(/*...*/);
</script>

Usage

Simple event bus registration with communication between a standard web component and a React component, as the event bus is framework agnostic. In addition a basic JSON schema draft-04 is used to restrict communication to a single boolean. Below outlines the basic usage, but can also be seen under /docs folder.

JSON Schema

{
  "type": "boolean"
}

Fragment One - Web Component

class PublisherElement extends HTMLElement {
  connectedCallback() {
    eventBus.register('namespace:eventName', { type: 'boolean' });
    this.render();
    this.firstChild && this.firstChild.addEventListener('click', this.send);
  }
  send() {
    eventBus.publish('namespace:eventName', true);
  }
  render() {
    this.innerHTML = `<button type="button">send</button>`;
  }
  disconnectedCallback() {
    this.firstChild && this.firstChild.removeEventListener('click', this.send);
  }
}

Fragment Two - React Component

import React, { useState, useEffect } from 'react';

function SubscriberComponent() {
  const [isFavorite, setFavorite] = useState(false);

  useEffect(() => {
    function handleSubscribe(favorite: boolean) {
      setFavorite(favorite);
    }
    eventBus.register('namespace:eventName', { type: 'boolean' });
    const sub = eventBus.subscribe<boolean>('namespace:eventName', handleSubscribe);
    return function cleanup() {
      sub.unsubscribe();
    };
  }, []);

  return isFavorite ? 'This is a favorite' : 'This is not interesting';
}

Advanced Schema

Following is an example of a more a more complex use-case with a larger JSON schema draft-04 and registration on multiple channels.

JSON Schema

{
  "type": "object",
  "required": ["name", "amount", "price"],
  "properties": {
    "name": {
      "type": "string"
    },
    "amount": {
      "type": "string"
    },
    "price": {
      "type": "number"
    },
    "organic": {
      "type": "boolean"
    },
    "stores": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [],
        "properties": {
          "name": {
            "type": "string"
          },
          "url": {
            "type": "string"
          }
        }
      }
    }
  }
}

Fragment - Angular Component

import { Component } from '@angular/core';
import eventSchema from './event-schema.json';

@Component({
  selector: 'app-store',
  template: '<button (onClick)="onSend()">Add to cart</button>',
})
export class StoreComponent implements OnInit, OnDestroy {
  private subs: { unsubscribe(): void }[] = [];

  ngOnInit() {
    // Register on add to cart channel
    eventBus.register('store:addToCart', eventSchema);

    // No need to register if no schema is required
    this.sub.push(eventBus.subscribe<boolean>('store:newDeals', this.onNewDeals));
  }

  onNewDeals() {
    /* handle new deals ... */
  }

  onSend() {
    eventBus.publish('store:addToCart', {
      name: 'Milk',
      amount: '1000 ml',
      price: 0.99,
      organic: true,
      stores: [
        {
          name: 'ACME Food AB',
          url: 'acme-food.com',
        },
      ],
    });
  }

  ngOnDestroy() {
    this.subs.forEach((sub) => sub.unsubscribe());
  }
}

API

Register

Register a schema for the specified event type and equality checking on subsequent registers. Subsequent registers must use an equal schema or an error will be thrown.

register(channel: string, schema: object): boolean;

Parameters

| Name | Type | Description | | ------- | -------- | ---------------------------------------------------- | | channel | string | name of event channel to register schema to | | schema | object | all communication on channel must follow this schema |

Returns - returns true if event channel already existed of false if a new one was created.


Unregister

Unregister the schema for the specified event type if channel exists.

unregister(channel: string): boolean;

Parameters

| Name | Type | Description | | ------- | -------- | ----------------------------------------------- | | channel | string | name of event channel to unregister schema from |

Returns - returns true if event channel existed and an existing schema was removed.


Subscribe

Subscribe to an event channel triggering callback on received event matching type, with an optional replay of last event at initial subscription. The channel may be the wildcard '*' to subscribe to all channels.

subscribe<T>(channel: string, callback: Callback<T>): { unsubscribe(): void };

subscribe<T>(channel: string, replay: boolean, callback: Callback<T>): { unsubscribe(): void };

Callbacks will be fired when event is published on a subscribed channel with the argument:

{
  channel: string,
  payload: T,
}

Parameters

| Name | Type | Description | | -------- | --------------- | --------------------------------------------------------------- | | channel | string | name of event channel to receive data from | | replay | boolean=false | flag indicating if initial description should return last event | | callback | function | function executed on when event channel receives new data |

Returns - object containing an unsubscribe method


Publish

Publish to event channel with an optional payload triggering all subscription callbacks.

publish<T>(channel: string, payload?: T): void;

Parameters

| Name | Type | Description | | ------- | -------- | ---------------------------------------- | | channel | string | name of event channel to send payload on | | payload | any | payload to be sent |

Returns - void


Get Latest

Get the latest published payload on the specified event channel.

getLatest<T>(channel: string): T | undefined;

Parameters

| Name | Type | Description | | ------- | -------- | ---------------------------------------------------------- | | channel | string | name of the event channel to fetch the latest payload from |

Returns - the latest payload or undefined


Get Schema

Get the schema registered on the specified event channel.

getSchema<T>(channel: string): any | undefined;

Parameters

| Name | Type | Description | | ------- | -------- | -------------------------------------------------- | | channel | string | name of the event channel to fetch the schema from |

Returns - the schema or undefined