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

ipc-messages-manager

v1.0.2

Published

Manage parent to child process (IPC) messages to be used as functions with callbacks

Downloads

9

Readme

ipc-messages-manager

Manage communication between parent and child processes through IPC asynchronously in NodeJS.

##Why?

When trying to use child process' functions from the parent process, you need to set up a bunch of listeners on both sides, and if you need to get a response to a specific function call asynchronously forget about it. Listening for messages does not allow to identify which response corresponds to which request(call to a child's function).

This packages solves this problem, allows you to easily call a function on a child process spawned with child_process.spawn(), and have a callback for it.

###Problem to solve:

(on parent process)

let child = spawn("node", ["./child.js"], {stdio:["pipe", "pipe", "pipe", "ipc"]});

child.send("asyncRequest1", "doSomething");

child.send("asyncRequest2", "doSomethingDifferent");

child.on("message", function(reponse){

	//this "response" is for asyncRequest1 or asyncRequest2???
	console.log(reponse);
});

##How to use it?

1.- Install it in your project:

npm install ipc-messages-manager -S

2.- Require it:

  • on parent process var ipcManager_parent = require("ipc-messages-manager").parent;

  • on child process var ipcManager_child = require("ipc-messages-manager").child;

3.- Spawn the child process (on parent process)

var child = require("child_process").spawn("node", ["./child-process.js"], {stdio:["pipe", "pipe", "pipe", "ipc"]});

4.- Send message from the parent to child:

ipcManager_parent.send(child, "actionToPerform", {param1:"foo", param2:"bar"}, function(result){
        console.log("response to this message was " + result);
    });

5.- Listen for this message on the child, and provide an answer to it:

ipcManager_child.actions.on("actionToPerform", function(args, callback){
	var result = doProcess(args.param1, args.param2);
	callback(result);
});

or, register a function to be called for each action, all at once:

ipcManager_child.setActions({
	"actionToPerform": function(args, callback){
		var result = doProcess(args.param1, args.param2);
		callback(result);
	},
	"secondActionToPerform": function(args, callback){
		doAsyncProcess(args.param1, function(result){
			callback(result);
		});
    }
});

##Parent's API ###send(child, action, args, callback)

####child Type: child_process

The child process to whom it will send the message, it should be a process spawned with child_process.spawn() method and with an IPC channel already setup

####action Type: String

A string to identify the action that needs to be performed on the child instance and answer back to the parent. For example, let's say the child has a addTwoNumbers() function and the parent wants to call it, then it is suggested to set action to be addTwoNumbers to make logical sense, but it's not required.

####args Type: Object

An object containing the arguments needed to perform "action". These arguments can later be retrieved on the child's listener function. In the example above for action addTwoNumbers, this args object could be something like {number1: 5, number2: 10}.

###callback([response]) Type: Function

Function to be called when the child responds back with an answer to this action(message)

The response object will be what the child sent back.

##Child's API

###setActions(actions)

####actions Type: Object

An object containing each action as keys and the value is the function that's going to be executed when that action is requested.

Each function takes 2 parameters, the first one is the args object which contains all arguments (or parameters) for the action requested, and the second one is the callback that needs to be called to return the response back to the parent.

var actions = {
addTwoNumbers: function(args, callback){
						var sum = addTwoNumbers(args.number1, args.number2);
						callback(sum);
					},
anotherAction: function(argsm callback){
						callback("anotherAction performed");
					},
...
}

###ipcManager_child.actions

Alternatively you can listen (and respond) for specific actions with the ipcManager_child.actions EventEmitter by listening with the on method in the following way:

ipcManager_child.actions.on("addTwoNumbers", function(args, callback){
	var sum = addTwoNumbers(args.number1, args.number2);
	callback(sum);
});

Questions

Feel free to open Issues to ask questions about using this package, PRs are very welcome and encouraged.

SE HABLA ESPAÑOL

License

MIT © Daniel Nieto