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

browser-message-broker

v1.0.112

Published

Simple message broker

Downloads

43

Readme

BMB - BrowserMessageBroker

⚠️ EXPERIMENTAL AND POORLY TESTED! Use at your own risk

Tests Published on npm

BMB is a tiny message broker (only about 2 kb compressed) that supports Publish/Subscribe and Request/Reply messaging patterns across multiple scripting contexts of the same origin (Tabs, Ifames, Service Workers, Dedicated and Shared Worker). It uses BroadcastChannel as a unified way of communication between different contexts.

Potential use cases

  • Communication between independent scripts or web components or micro frontends
  • Communication between multiple tabs and workers or iframes

Features

  • Publish/Subscribe
  • Request/Reply
  • Messages caching and automatic synchronisation of the contexts

Examples

See /examples/todo-app in this repo

Todo-app example readme

Demo

Getting started

Install:

npm install browser-message-broker --save

Publish/Subscribe

MyMessageProducer.ts

import { PubSubChannel, ReqRepChannel } from "browser-message-broker";
type MyMessage = { name: string; greeting: string }
const MyMessageChannel = PubSubChannel.for<MyMessage>(
  "MyMessage", {
    broadcast: true,
    cache: false,
    trace: false
  }
);

MyMessageChannel.publish({ name: "Foo", greeting: "Hi!" });

Or, just publish/broadcast using default channel settings

PubSubChannel.publish("MyMessage", { name: "Foo", greeting: "Hi!" });
//or
PubSubChannel.broadcast("MyMessage", { name: "Foo", greeting: "Hi!" });

MyMessageConsumer.ts

import { PubSubChannel, ReqRepChannel } from "browser-message-broker";
type MyMessage = { name: string; greeting: string }
const MyMessageChannel = PubSubChannel.for<MyMessage>(
  "MyMessage", {
    broadcast: true,
    cache: false,
    trace: false
  }
);

MyMessageChannel.subscribe((msg: MyMessage)=>{
    console.log(msg)
})

Request/Reply

import { PubSubChannel, ReqRepChannel } from "browser-message-broker";

type TReq = { reqPayload: string };
type TRep = { respPayload: string };

// Shared Worker (consumer)
ReqRepChannel.for<TReq, TRep>(
  "GetData", 
  { broadcast: true }
).reply((req: TReq)=>{
  return  { respPayload: "Hello " + req.reqPayload   }
});

// Window (producer)
const req: TReq = { reqPayload: "Bob" };

const reply: TResp = 
await ReqRepChannel.for<TReq, TRep>(
 "GetData", 
 { broadcast: true }
).request(undefined);

console.log(reply)// { "respPayload": "Hello Bob" }