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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@bytemend/mfebus

v1.4.5

Published

In-memory pub-sub for Node with pluggable transports — child_process / worker_threads IPC, EventEmitter, browser cross-frame

Readme

@bytemend/mfebus

In-memory pub-sub for Node. Synchronous same-process dispatch, plus pluggable transports so the bus can extend across child_process, worker_threads, MessagePort, or — when running in the browser — postMessage boundaries.

When the package is loaded inside a fork()-spawned child (process.send defined), it auto-binds to the parent channel. No setup needed for the common worker-pool pattern.

Install

npm i @bytemend/mfebus

Same-process

import { emit, on } from '@bytemend/mfebus';

const off = on('job:done', (payload, meta) => {
  console.log('job', payload.id, 'finished', meta.local ? '(local)' : `(from ${meta.senderId})`);
});

emit('job:done', { id: 42 });
off();

Node IPC — worker_threads

import { Worker } from 'node:worker_threads';
import { addIpcTarget, on } from '@bytemend/mfebus';

const worker = new Worker(new URL('./worker.js', import.meta.url));
const remove = addIpcTarget(worker);

on('worker:status', (s) => console.log('[main]', s));

// inside worker.js — `addIpcTarget(parentPort)` plus `emit('worker:status', …)`
// is enough to reach the listener above.

Node IPC — child_process.fork

import { fork } from 'node:child_process';
import { addIpcTarget } from '@bytemend/mfebus';

const child = fork('./child.js');
addIpcTarget(child);

// inside child.js the package auto-binds to `process` because
// `process.send` is defined under fork(). Just import and use.

Custom transport (Redis, NATS, etc.)

import { addTransport } from '@bytemend/mfebus';

addTransport({
  send: (envelope) => redis.publish('events', JSON.stringify(envelope)),
  onMessage: (cb) => {
    const onMsg = (_, raw) => cb(JSON.parse(raw));
    redis.on('message', onMsg);
    redis.subscribe('events');
    return () => redis.off('message', onMsg);
  },
});

Browser cross-frame (optional)

When loaded in a browser context, the bus also listens for window.postMessage. Register the peer window once:

import { addCrossFrameTarget, setAllowedOrigins } from '@bytemend/mfebus';

const frame = document.querySelector('#peer');
if (frame?.contentWindow) addCrossFrameTarget(frame.contentWindow);

// Tighten in production:
setAllowedOrigins(['https://peer.example.com']);

API

emit<T>(event: string, payload?: T): void
on<T>(event: string, handler: (p: T, meta) => void): () => void
once<T>(event: string, handler: (p: T, meta) => void): () => void
off(event: string, handler?: Handler): void
clear(event?: string): void

addTransport(transport: { send(env), onMessage?(cb) → off }): () => void
addIpcTarget(channel): () => void   // Worker | ChildProcess | MessagePort

addCrossFrameTarget(target): void
removeCrossFrameTarget(target): void
setAllowedOrigins(origins: string[]): void

senderId: string

Handler meta

type DispatchMeta = {
  senderId: string;        // random per-load id of the emitter
  local: boolean;          // came from the same process / frame?
  origin?: string;         // window origin (browser cross-frame only)
  ts?: number;             // posting timestamp (transport dispatches)
  transport?: unknown;     // handle of the transport that delivered the envelope
};

Notes

  • Handlers run in registration order. Exceptions are caught and logged — one bad subscriber can't kill the bus.
  • The bus drops envelopes whose senderId matches the local id, so transports that loop back are safe.
  • setAllowedOrigins(['*']) is the dev default; tighten in production for browser frames.

License

MIT.