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

@mszmaj/mediatsion

v0.1.2

Published

An in-process mediator/pipeline library for Typescript and NodeJS.

Downloads

4

Readme

mediaTSion

An in-process mediator/pipeline library for Typescript and NodeJS.

NOTE: Work in progress

Pre-requisites

IMPORTANT: reflect-metadata must be imported at the start of the application and only once.

Packages

Install reflect-metadata:

npm install reflect-metadata

Install mediatsion:

npm install mediatsion

How-To:

1A. Create new Request:

class ExampleRequest implements IRequest<ExampleInput, ExampleResult> {
    request: ExampleInput = new ExmapleInput();
    result: ExampleResult = new ExampleResult();
}

class ExampleInput implements IInput {
    example: string;
}

class ExampleResult implements IResult {
    id: string;
}

1B. Create new Event:

class ExampleEvent implements IEvent {
    example: string
}

2A. Create a new Command/Request Handler:

@requestHandler('ExampleRequest','ExampleResult')
class ExampleCommandHandler implements IRequestHandler<ExampleRequest, ExampleResult>  {
    async handleAsync(): Promise<Result<ExampleResult, Error>> {
        let result: Result<ExampleResult, Error>;
        try {
            //do stuff
            result = Ok(returnModel);
        } catch (error) {
            result = Err(new Error());
        } 
        
        return result;
    }
}

NOTE: Currently you need to pass in the name of the Request and Result objects as strings.

NOTE: The name of the handler; while it is a IRequestHandler it might be best to name it either *CommandHandler or *QueryHandler for readability. Typically Commands will not provide a Result object.

2B. Create a new Event handler:

@eventHandler('ExampleEvent')
class ExampleEventHandler implements IEventHandler<ExampleEvent>  {
    async handleAsync(): Promise<void> {
        //do stuff
    }
}

NOTE: Currently you need to pass in the name of the Event object as a string.

3. Use Bus to mediate:

import { Bus } from mediatsion;

const bus: Bus = new Bus();
const exampleRequestHandler = new ExampleRequestHandler();
const requestResult = await bus.send(exampleRequestHandler);

const exampleEvent = new ExampleEvent;
const eventResult = await bus.publish(exampleEvent); //NOTE: this will always be a void array. Only check for result.ok.

3A. Create a publish strategy:

A strategy will allow you to run event handlers in a different order than registered. This will allow you to run them in parallel as well.

const strategy = async (handlers: IEventHandler<TestEvent>[], event: IEvent): Promise<Array<void>> => {
        const result: Array<void> = [];
        for (let i = handlers.length-1; i >= 0; i--) {
            result.push(await handlers[i].handleAsync(event));
        }
        return result;
    }

const reuslt = await bus.publish(exampleEvent, strategy);

Release Notes:

0.1.2:

  • Publish strategies

Roadmap:

0.1.3:

  • Pipeline functionality

1.0.0:

  • Production ready release