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

forks-communicator

v0.1.2

Published

Node.js fork and worker communicator (messages between processes)

Downloads

2

Readme

Node.js fork communicator (messages between processes)

Small library for communication between forks. This library is created for small projects that do not need to store queues and no guarantee of receipt. For more complex tasks, use rabbitmq or another message-broker.

Install

npm install forks-communicator --save

Usage examples

Examples available here!

Just clone, go to the example directory and run fork.js or worker.js.

fork.js - Fork example

Create master and forks then wrap forks to the communicator. For master use forks-communicator and for forks forks-communicator/fork.

const { setup, subscribe, emit } = require("forks-communicator");
const { fork } = require("child_process");
const { join } = require("path");

// Wrap forks in the communicator
setup(fork(join(__dirname, "/child/process.js")));
setup(fork(join(__dirname, "/child/another_process.js")));

// Subscribe to channels from master process
subscribe("say", ({ message }) => console.log(`[master] recived: ${message}`));
subscribe("requestYeah", () => {
  // Send message from master to all subscribtions
  emit("all", "yeah");
});

worker.js - Worker example

Create master and forks then wrap forks to the communicator. For master use forks-communicator and for forks forks-communicator/fork.

const { setup, subscribe, emit } = require("../index");
const { Worker } = require("worker_threads");
const { join } = require("path");

// Wrap forks in the communicator
setup(new Worker(join(__dirname, "/child/process.js")));
setup(new Worker(join(__dirname, "/child/another_process.js")));

// Subscribe to channels from master process
subscribe("say", ({ message }) => console.log(`[master] recived: ${message}`));
subscribe("requestYeah", () => {
  // Send message from master to all subscribtions
  emit("all", "yeah");
});

child/process.js

const { emit, subscribe } = require("forks-communicator/fork");

// Subscribe to channel from fork process
subscribe("all", ({ message }) => {
  console.log(`[fork] Message for all ${message}`);
});

// Emit message to "say" channel from fork process
emit("say", "[fork] Meow from fork");

// Emit message to "meow" channel after second from fork process
setTimeout(() => {
  emit("meow", "[fork] Meow to another fork");
}, 1000);

child/another_process.js

const { emit, subscribe } = require("forks-communicator/fork");

const all = subscribe("all", ({ message }) => {
  console.log(`[another fork] Message for all ${message}`);
});

subscribe("meow", ({ message }) => {
  console.log(`[another fork] Meow recived: ${message}`);
  emit("requestYeah");

  // Unsubscribe fork :)
  all.unsubscribe();
});

emit("say", "[another fork] Meow from another fork");

Work result

[master] recived: [fork] Meow from fork
[master] recived: [another fork] Meow from another fork
[another fork] Meow recived: [fork] Meow to another fork
[fork] Message for all yeah