![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@moirae/node-plugin
Advanced tools
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.
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.
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, and Queries must be duplicated across all systems as the DTOs are key for the usage of Moirae.
FAQs
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.
We found that @moirae/node-plugin demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.