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

@beetech/cqrs

v0.0.11

Published

BeeTech CQRS framework

Downloads

12

Readme

Bee CQRS

This is a simple CQRS framework with a Command and a Query bus.

Motivation

There are a lot of CQRS frameworks for JavaScript out there, this is not new. The one thing we're trying to achieve here is the ability to take advantage of such a framework but without coupling it into the application's domain. The main goal here is to create a framework that you can use without injecting any dependencies into your domains.

Getting started

Install it using npm:

npm install @beetech/cqrs

Usage

Let's use a coupled example to show how the types are glued together.

import { InMemoryHandlerRegistry, QueryBus, QueryHandler } from '@beetech/cqrs';

export class Multiplier {
    public constructor(
        public readonly value: number,
        public readonly factor: number,
    ) {}
}

export class MultiplierHandler implments QueryHandler<Multiplier, number> {
    public query(query: Multiplier): number {
        return query.value * query.factor;
    }
}

const registry = (new InMemoryHandlerRegistry<QueryHandler<any, any>>())
    .register('Multiplier', multiplierHandler);

const queryBus = new QueryBus(registry);
const result = queryBus.query(new Multiplier(5, 4));
// result should be equal to 20

You can see that MultiplierHandler is implementing an interface called QueryHandler, right? This is an example of a "coupled" implementation. Imagine this being used inside your domain, you'll have a domain importing an external library and that's not ideal.

By taking advantage of TypeScript's gererics, we were able to create a structure that will work event if you don't explicitly implements our interface. Here's the same example but not coupled:

import { InMemoryHandlerRegistry, QueryBus, QueryHandler } from '@beetech/cqrs';

export class Multiplier {
    public constructor(
        public readonly value: number,
        public readonly factor: number,
    ) {}
}

export class MultiplierHandler {
    public query(query: Multiplier): number {
        return query.value * query.factor;
    }
}

const registry = (new InMemoryHandlerRegistry<QueryHandler<any, any>>())
    .register('Multiplier', multiplierHandler);

const queryBus = new QueryBus(registry);
const result = queryBus.query(new Multiplier(5, 4));
// result should be equal to 20

As you can see, the query and the query handler have nothing to do with the CQRS framework, all the bindings will be where they belong: inside the application layer and not on the domain layer.

It's a subtle but, at the same time, huge difference.