fork() does not emit 'error' if process creation fails

[rus0000]

• Version: v8.6.0
• Platform: Linux 4.4.0-78-generic How about an io.js podcast to help us keep up? #99~14.04.2-Ubuntu SMP Thu Apr 27 18:49:46 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
• Subsystem: child_process

Unlike spawn in fork on error is not executed.

const { fork } = require('child_process');
const subprocess = fork('bad_command');

subprocess.on('error', (err) => {
    console.log('Failed to start subprocess.', err);
});

[evanlucas]

do you get the same error on v8.5.0?

[cjihrig]

The problem is that fork() spawns node, which works. The child process throws an exception when it tries to require() the module that does not exist. The child process exits with a non-zero status code.

[bnoordhuis]

What Colin said. I'll close this out as 'working as intended.' If anyone feels this ought to be documented, please open a documentation pull request.