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

@moirae/node-plugin

v0.6.0

Published

NodeJS port of Moirae Core module to enable usage in non-NestJS environments. Note this is not the ideal configuration and should only be used in edge cases.

Downloads

3

Readme

@moirae/node-plugin

NodeJS port of Moirae Core module to enable usage in non-NestJS environments. Note this is not the ideal configuration and should only be used in edge cases.

Supported Features

  • [ ] AggregateFactory
  • [ ] Command Execution
  • [x] Command Listening
  • [ ] Event Listening
  • [ ] Event Persistence
  • [ ] Event PubSub
  • [ ] Query Execution
  • [x] Query Listening

Setup

Moirae requires more advanced configuration when operating in this mode. As an example with RabbitMQ:

const {ObservableFactory} = require('@moirae/core');
const {MoiraePlugin} = require('@moirae/node-plugin');
const {RabbitMQConnection, RabbitMQPublisher} = require('@moirae/rabbitmq');

// Define the parameters of the connection and initialize it
const rabbitMQConfig = {/* config contents */};
const connection = new RabbitMQConnection(rabbitMQConfig);

const moirae = new MoiraePlugin({
    domains: ["myApp"],
    // Provide a way to instantiate new Publisher instances
    getCommandPublisher: () =>
        new RabbitMQPublisher(new ObservableFactory(), rabbitMQConfig, rmqConnection),
    getEventPublisher: () =>
        new RabbitMQPublisher(new ObservableFactory(), rabbitMQConfig, rmqConnection),
    getQueryPublisher: () =>
        new RabbitMQPublisher(new ObservableFactory(), rabbitMQConfig, rmqConnection)
});

// Add Query/Command handlers
moirae.injectCommandHandler(...);
moirae.injectQueryHandler(...);

// Initialize
await rmqConnection.onModuleInit();
await moirae.init();

// ... App logic ...

// Teardown
await rmqConnection.onApplicationShutdown();
await moirae.tearDown();

When operating in a non-NestJS environment, the plugin must compensate for the lack of a Dependency Injection container and therefore creates one itself. However the user must provide some key elements: namely the publisher and event store as they must be created independently of Moirae.

Additionally the lifecycle methods of NestJS may need to be managed independently. In the above example, the connection lifecycle methods of onModuleInit and onApplicationShutdown are not called for the RabbitMQConnection automatically. These methods are handled for all elements gotten from the MoiraePlugin, including the Publishers generated on startup.

Commands, Events, Queries

Commands, Events, and Queries must be duplicated across all systems as the DTOs are key for the usage of Moirae.