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

cqrs-flow

v2.0.3

Published

a toolkit for managing cqrs events and commands

Readme

cqrs-toolkit

a toolkit that eases managing cqrs events and commands

Features:


  • Event Bus:
  • Command Bus:
  • ICommand/IEvent interface

Handling multiple events with v2

Pass multiple event classes to EventHandlerV2 to route them to the same handler:

@EventHandlerV2([OrderCreated, OrderCancelled])
class OrderEventHandler implements IEventHandler<IEvent> {
  async handle(event: IEvent) {
    if (event instanceof OrderCreated) {
      // Handle creation.
    } else if (event instanceof OrderCancelled) {
      // Handle cancellation.
    }
  }
}

Passing a single event remains supported: @EventHandlerV2(OrderCreated).

Handling one event with multiple v2 handlers

Decorate multiple handler classes with the same event to fan out each dispatch:

@EventHandlerV2(OrderCreated)
class SendConfirmation implements IEventHandler<OrderCreated> {
  async handle(event: OrderCreated) {
    return `confirmation:${event.name}`;
  }
}

@EventHandlerV2(OrderCreated)
class UpdateReporting implements IEventHandler<OrderCreated> {
  async handle(event: OrderCreated) {
    return `reporting:${event.name}`;
  }
}

const results = await eventBus.handle<string>(new OrderCreated());

Handlers run concurrently. results contains their resolved values in registration order. If any handler rejects, the dispatch rejects after all handlers have already been started. Dispatching an event with no registered handlers also rejects.