Currently, Node.ChildProcess.spawn with a non-existent executable will return a ChildProcess which isn't "real". For example, its pid will be undefined. This is not ideal.

Currently, you have to handle this by calling onError. Unfortunately, onError is used for other failure conditions that do not happen immediately; see the Node docs.

It's not currently clear to me how best to handle this.