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

mps-nestjs-cqrs

v1.0.1

Published

A lightweight CQRS module for Nest framework (node.js)

Downloads

27

Readme

Description

A fork of the original @nestjs/cqrs package that uses the names of queries and commands instead of a generated uuid. The pros of this version that handlers are mapped by command/query name which let you resolve them by name instead of type without losing any performance and can let you map your commands/queries without using nestjs controllers. The consequence is that commands and queries names needs to be unique.

What's new

CommandBus

resolveCommandTypeByName(name: string): Type<ICommand>;
// throw CommandHandlerNotFoundException if the command wasn't found

QueryBus

resolveQueryTypeByName(name: string): Type<IQuery>;
// throw QueryHandlerNotFoundException if the query wasn't found

Magic Trick example

const commandName = 'test';
const body = { value: 1 };

// resolve command
let command: ICommand;
try {
  const commandType = this.commandBus.resolveCommandTypeByName(commandName);
  // plainToClass from class-transformer package
  command = plainToClass(commandType, body);
  commandResult = await this.commandBus.execute(command);
} catch(error) {
  if (error instanceof CommandHandlerNotFoundException) {
    // command not found, do something here
  }
  throw error;
}

Installation

$ npm install --save mps-nestjs-cqrs

License

Nest is MIT licensed.