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

@dkx/command-bus

v1.0.0

Published

Simple command bus for node.js

Downloads

7

Readme

DKX/CommandBus

Simple command bus for node.js

Installation

$ npm install --save @dkx/command-bus

or with yarn

$ yarn add @dkx/command-bus

Commands

Command should be just a simple value object implementing the Command interface.

import {Command} from '@dkx/command-bus';
import {User} from './user';

class UpdateUserNameCommand implements Command
{
    constructor(
        public readonly user: User,
        public readonly name: string,
    ) {}
}

Handlers

There is always one handler for one command and it must implement the Handler interface.

import {Handler, Command} from '@dkx/command-bus';
import {User} from './user';
import {UpdateUserNameCommand} from './update-user-name-command';

class UpdateUserNameHandler implements Handler<User>
{
    public handle(command: UpdateUserNameCommand): User
    {
        const user = command.user;
        const name = command.name;
        
        // todo: store in DB
        user.name = name;
        
        return user;
    }
}

The handle method can return Promise too.

Usage

When you have both command and handler, you need to register them in command bus.

import {CommandBus, WeakMapMapper} from '@dkx/command-bus';
import {UpdateUserNameCommand} from './update-user-name-command';
import {UpdateUserNameHandler} from './update-user-name-handler';

const mapper = new WeakMapMapper;
mapper.add(UpdateUserNameCommand, () => new UpdateUserNameHandler);

const bus = new CommandBus(mapper);

First argument to add method is the command itself. The second argument is factory function which must return instance of the associated handler.

Now you can let the command bus handle the action:

const updatedUser = await bus.handle(new UpdateUserNameCommand(
    user,
    'John Doe',
));

As you can see, we use the await here, because handle method always returns a Promise.

Middlewares

Middleware can be used to wrap the handle callback into custom method. This is useful for example for logging or maybe running whole handlers stack in one database transaction. Middleware is class that must implement the Middleware interface.

The actual handler is called as a last middleware.

import {Middleware, MiddlewareNextCallback, Command} from '@dkx/command-bus';

class DatabaseTransactionMiddleware implements Middleware
{
    public async apply<T>(command: Command, next: MiddlewareNextCallback<T>): Promise<T>
    {
        console.log('Before handler');
        
        let result: T;
        await runInTransaction(async () => {
            result = await next();
        });
        
        console.log('After handler');
        
        return result;
    }
}

bus.use(new DatabaseTransactionMiddleware);

apply method must always return a Promise and should call the next middleware.

Simple logging middleware could look like this:

import {Middleware, MiddlewareNextCallback, Command} from '@dkx/command-bus';

class LoggingMiddleware implements Middleware
{
    public async apply<T>(command: Command, next: MiddlewareNextCallback<T>): Promise<T>
    {
        console.log('Running command');
        console.log(command);
        
        return next();
    }
}

bus.use(new LoggingMiddleware);