I fear this could reintroduce the bug that #214 fixed.

Perhaps try something like this:

var stdoutEnded = false, stderrEnded = false;
function tryClosing() {
  if (stdoutEnded && stderrEnded) {
    stdoutStream.end();
  }
}
childProcess.stdout.on('end', function() {
  stdoutEnded = true;
  tryClosing();
});
childProcess.stderr.on('end', function() {
  stderrEnded = true;
  tryClosing();
});

@devtristan, whilst this did not explicitly reintroduce the bug fixed by #214, it was indeed misguided in its reliance on process.stdout.

Your solution is much more elegant and relevant; applying your fix + outputting to console on stdStream.end() seems to confirm the validity of this fix in the context of chained git commands.

Pull request updated accordingly!

thanks @JulianLaval and @devtristan !

this is now published in v0.5.3