node package manager
Easy sharing. Manage teams and permissions with one click. Create a free org »



spawn.js aims to make multi-process programming with Node.js a joy.

The library allows you to spawn any function in a new Node.js instance.

You get back an EventEmitter that you can use to communicate with the spawned worker.


var spawn = require('spawn');
var helloWorldFunction = function(events) {
  events.on('talk_to_me', function() {
    events.emit('worker_message', 'hello_world');
// spawn helloWorldFunction in a new process: 
var helloWorldWorker = spawn(helloWorldFunction);
// listen on the helloWorldWorker's EventEmitter: 
helloWorldWorker.on('worker_message', function(message) {
// emit an event that gets propagated to the worker: 

When spawning a function, spawn.js essentially returns you an EventEmitter that gets synced between the master and child process.

So in the example above 'helloWorldWorker' and the 'events' parameter in 'helloWorldFunction' are EventEmitters synced to each other.


You can access the module by doing:

var spawn = require('spawn');


var anEventEmitter = spawn(aWorkerFunction);

Spawns a new process running aWorkerFunction by passing it an EventEmitter. A synced version of the same EventEmitter gets returned in the spawning master process. All emits on the returned EventEmitter get copied to the workerFunction's emitter.

var anEventEmitter = spawn(aWorkerModulePath);

Spawns a new process by running the function defined in aWorkerModulePath. When using this function to spawn a worker you avoid the network and serialization overhead of passing the worker function to the new process. But its of course only half as sexy as having it all defined in one source file...

worker function:

function(anEventEmitter) { }

As the function will get executed within a new Node instance you should not reference anything outside the function's lexical scope.

worker module:

If you pass a path to spawn you need to have a module defined like this:

module.exports = function(anEventEmitter) { }


The event emitters passed to the worker function and returned by spawn, behaves as described in the Node.js documentation. As all events are copied between the master's and child's version of the emitter you may only pass objects as event parameters that can be serialized to JSON.

There are only two reserved events on the synced EventEmitters: #### Event: 'terminate'

function() { }

Emitting this event will terminate the worker.

Event: 'terminated'

function() { }

This event will be emitted when the worker has been terminated.


Instead of rolling our own custom protocol we rely on the WebWorker API for any communication with spawned workers.

Many thanks to Peter Griess' excellent node-webworker module implementing the WebWorker API - we use a slightly modified version of his library.