Child Process Require

Require a function and run it in a child process.

This is a way to take lengthy, cpu intensive tasks and run them in a child process. Allowing you to take advantage of multiple cpu cores. Child Process Require (cpr) will let you require a function from a file and run it in a new node process each time you call it. Almost as if it were all in a single process.

• Each execution of a required function starts a new node process
• The function's return value will be wrapped in Promise.
• Arguments can be any JSON data type or callback function.
• Environment variables are shared
• stdin, stdout and stderr are shared (so console.log, console.error, etc will work)
• Crashes will become promise rejections
• Rejections of error objects will be recreated with stack traces
• If you process.exit or crash an attempt will be made to stop the child process

It works like this

// work.js should have a single function exported that returns a value or a Promise.
// It can have data or functions for arguments
module.exports = function add(a, b) {
  return Promise.resolve(a + b)
}

// main.js can now start a child processes to do the work.
// `require.resolve` returns the absolute path of `work.js`
// the absolute path is required for for child process require to work
const cpr = require('child-process-require')
const absolutePath = require.resolve('./work')
const work = cpr(absolutePath)

Promise.all([
  work(1, 2),
  work(2, 3),
  work(3, 4)
]).then(console.log)
// [3, 5, 7]

Arguments and return values are passed between node processes using NodeJs's child process IPC channel and the dnode protocol. This means all objects will be JSON stringified and parsed. Rejected Error objects will be converted back into error objects with their message, stack traces and all iterable properties preserved. The dnode protocol allows for circular references and callback functions. (Functions who's return value isn't needed.)

API

• childProcessRequire(path, [opts]) returns a function that takes any arguments and passes them to the default export or module.export of file at the path. Returns a promise that resolves to the return of the remote function
• opts.nodeBin optional binary to run for nodejs, defaults to process.argv[0]. This is a perfect place to specify the binary for an alternate version of node. When this issue closes you'll be able to use babel-node here but for now it doesn't work.
• opts.requires An array of strings of package names to require before requiring your function's file. This is the perect place for babel-register.
• opts.env An object of env vars to copy into the child process's copy of process.env

Todo

• Better API docs
• Expose execa's options including timeouts
• Test to see if alternative nodejs runtimes work (etc, babel-node)
• See if we can extend dnode-protocol to handle promises, dates and error objects
• See if we can support some subset of arbituary exports of the requied file
• See what people think