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

@universis/racket

v1.3.3

Published

Universis project inter-process events

Downloads

163

Readme

@universis/racket

An inter-process event service which implements the communication between processes by sending and receiving messages in an active inter-connector environment.

@universis/racket

This implementation is very important for applications and services which are running in cluster mode and every cluster worker should inform cluster for something.

Install

npm i @universis/racket

Usage

InterProcessEventEmitter

InterProcessEventEmitter handles process events and emits them even if process is running in cluster mode or under pm2. Each worker of a cluster or the process itself has the option to handle inter-process events by using InterProcessEventEmitter.subscribe().

Register globally InterProcessEventEmitter handler:

import { InterProcessEventEmitter } from './InterProcessEventEmitter';
InterProcessEventEmitter.register();

or use @universis/racket/register as --require script under nodejs

node --require @universis/racket/register myapp.js

Start sending process events

import { InterProcessEventEmitter } from '@universis/racket';

new InterProcessEventEmitter().emit({
    body: 'Hello World!'
});

or subscribing for new events

import { InterProcessEventEmitter } from '@universis/racket';

const emitter = new InterProcessEventEmitter().subscribe((message) => {
    // write your code here
});

...
emitter.unsubscribe();

ProcessEventEmitter

ProcessEventEmitter uses @universis/racket service to send and receive process events. @universis/racket event service is an HTTP service which acts as a proxy of all events emitted by any client of that service. Process events are being collected by the service and transmitted to any client that has been subscribed for receiving messages.

Start @universis/racket/platform-server as a standalone service

npx @universis/racket/platform-server/register

or register @universis/racket/platform-server under pm2

pm2 start @universis/racket/platform-server/register -n racket

This operation will start an instance of @universis/racket service which is a typical HTTP service and starts listening for process subscription under http://localhost:14440

ProcessEventEmitter.subscribe

Any process may use ProcessEventEmitter class and subscribe for new events:

import { ProcessEventEmitter } from '@universis/racket';

const subscription = new ProcessEventEmitter().subscribe((event) => {
    // write your code here
});

// unsubscribe
subscription.unsubscribe();

When service has been configured to run in different port use serviceHost param to define service host:

import { ProcessEventEmitter } from '@universis/racket';

const subscription = new ProcessEventEmitter('http://localhost:12345/').subscribe((event) => {
    // write your code here
});

ProcessEventEmitter.emit

Use ProcessEventEmitter.emit(event) for sending messages to all subscribers:

new ProcessEventEmitter().emit({
    type: 'message',
    value: {
        body: 'Hello World!'
    }
});