
Security News
The Next Open Source Security Race: Triage at Machine Speed
Claude Opus 4.6 has uncovered more than 500 open source vulnerabilities, raising new considerations for disclosure, triage, and patching at scale.
It's easy to fork a list of child process for node.js by ForkList.
var ForkList = require('fork-list');
// which script to run by multiprocess
var path = './script/write';
// child process num
var num = 3;
var forks = new ForkList({
path: path,
num: num
});
for (var i = 0; i < 10; i++) {
forks.send('hello~', i);
}
forks.shutdown();
the ./script/write.js is:
var Forks = require('fork-list');
Forks.proc(function(data1, data2) {
console.log('Work id:', this.workid, 'recv data1:', data1, 'data2:', data2);
});
Output:
Work id: 1 recv data1: hello~ data2: 1
Work id: 2 recv data1: hello~ data2: 0
Work id: 0 recv data1: hello~ data2: 5
Work id: 1 recv data1: hello~ data2: 2
Work id: 2 recv data1: hello~ data2: 3
Work id: 1 recv data1: hello~ data2: 9
Work id: 2 recv data1: hello~ data2: 4
Work id: 0 recv data1: hello~ data2: 6
Work id: 2 recv data1: hello~ data2: 7
Work id: 2 recv data1: hello~ data2: 8
newcountsetClassifiersetLoggersendforwardprockillByPidshutdownonExitonErroronFinishfork a new process with specify path.
get total number of processes.
set special classifier.
enable or disable fork-list debug log, or set your special logger such as log4js.getLogger.
var ForkList = require('fork-list');
var underscore = require('underscore');
var times = 10;
var forks = new ForkList();
forks.new('./script');
forks.new('./script');
forks.setClassifier(function(msg, done) {
var id = underscore.random(0, forks.count() - 1);
done(null, id);
});
for (var i = 0; i < times; i++) {
forks.send(i, 'some msg');
}
forks.shutdown();
Master: transfor usal data.
Master: transfor usal data.
Subprocess: get data from master.
This will forcely kill special child process, and don't care if there are some jobs haven't done.
This will forcely shutdown all child process, and don't care if there are some jobs haven't done.
Example:
var ForkList = require('fork-list');
var path = './script';
var num = 3;
var forks = new ForkList({
path: path,
num: num,
log: true
});
for (var i = 10; i >= 0; i--) {
forks.send('hello ' + i);
};
forks.on('error', function(err, pid) {
console.log('--> Error:', err.message, 'pid:', pid);
});
forks.on('exit', function(pid) {
console.log('--> Child process exit, pid:', pid);
forks.killByPid(pid);
});
forks.on('finish', function() {
console.log('--> All of child process has exited');
});
forks.shutdown();
script.js
var Forks = require('fork-list');
Forks.proc(function(data1, data2) {
console.log('Work id:', this.workid, 'recv data1:', data1);
});
Output:
Work id: 0 recv data1: hello 10
Work id: 0 recv data1: hello 8
Work id: 0 recv data1: hello 7
Work id: 2 recv data1: hello 9
Work id: 0 recv data1: hello 6
Work id: 1 recv data1: hello 5
Work id: 0 recv data1: hello 2
Work id: 0 recv data1: hello 0
Work id: 1 recv data1: hello 4
Work id: 1 recv data1: hello 3
Work id: 1 recv data1: hello 1
--> Child process exit, pid: 15064
--> Error: IPC channel is already disconnected pid: 15064
--> Child process exit, pid: 13072
--> Error: IPC channel is already disconnected pid: 13072
--> Child process exit, pid: 4900
--> Error: IPC channel is already disconnected pid: 4900
--> All of child process has exited
FAQs
Easy to fork a list of child process
We found that fork-list demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
Claude Opus 4.6 has uncovered more than 500 open source vulnerabilities, raising new considerations for disclosure, triage, and patching at scale.

Research
/Security News
Malicious dYdX client packages were published to npm and PyPI after a maintainer compromise, enabling wallet credential theft and remote code execution.

Security News
gem.coop is testing registry-level dependency cooldowns to limit exposure during the brief window when malicious gems are most likely to spread.