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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@valts/message-bus

v1.0.0

Published

A framework-agnostic, type-safe implementation of a message bus for event-driven architecture

Downloads

7

Readme

Message Bus

Framework agnostic implementation of a message bus. Allow communication between components without tight coupling.

How it works

The message bus is a singleton instance that can be used to send and receive messages. It is responsible for routing messages to the correct handlers. For any message you should define a topic, and a payload type mapped to it.

  1. Subscribers register to a topic via the subscribe method.
  2. Publishers emit events to specific topics using the event method.
  3. The registry maintains the mapping between topics and subscribers.
  4. When an event is published, all active subscribers to that topic get notified.

Get started

A good practice is to start by defining the topic map, and then use the message bus with it to ensure full type safety. As your application grows, you can add more topics and payload types to it. If you skip this step, you'll still get the record but without strict type safety.

type TopicMap = {
  "user.profile.updated": {
    payload: {
      id: string;
    };
  };
};

// create the message bus with the topic map
const messageBus = messageBus<TopicMap>();

// subscribe to a topic
messageBus.subscribe("user.profile.updated", async (message) => {
  // access the typed payload
  console.log(message.payload.id);
});

// emit an event to a topic
await messageBus.event("user.profile.updated", {
  id: "123",
});

And that's it.