Currently, returned promise resolves immediately after first 'data' event which in my opinion is not correct — you simply can not get further output from child process. This PR makes use of deferred.notify instead of deferred.resolve for child process output forwarding purposes and resolves promise only when process exits.
Currently, returned promise resolves immediately after first 'data' event which in my opinion is not correct — you simply can not get further output from child process. This PR makes use of deferred.notify instead of deferred.resolve for child process output forwarding purposes and resolves promise only when process exits.