Use callback from empty write instead of drain event but don't prevent f...

README.md

@@ -22,10 +22,6 @@ console.error("yay");
 
 // process.exit(5);
 exit(5);
-
-// These lines shouldn't appear in the output.
-console.log("wtf");
-console.error("bro");
 ```
 
 ## Don't believe me? Try it for yourself.

lib/exit.js

@@ -18,13 +18,11 @@ module.exports = function exit(exitCode, streams) {
     }
   }
   streams.forEach(function(stream) {
-    // Prevent further writing.
-    stream.write = function() {};
     // Count drained streams now, but monitor non-drained streams.
     if (stream.bufferSize === 0) {
       drainCount++;
     } else {
-      stream.once('drain', function() {
+      stream.write('', 'utf-8', function() {
         drainCount++;
         tryToExit();
       });

test/exit_test.js

@@ -83,15 +83,13 @@ function buildTests() {
       pipes.forEach(function(pipe) {
         var command = 'node log.js 0 ' + count + output + ' 2>&1' + pipe;
         exports['exit']['output (' + command + ')'] = function(test) {
-          test.expect(2);
+          test.expect(1);
           run(command, function(code, actual) {
             var expected = fixture(count + output.replace(/ /g, '-') + '.txt');
             // Sometimes, the actual file lines are out of order on Windows.
             // But since the point of this lib is to drain the buffer and not
             // guarantee output order, we only test the length.
             test.equal(actual.length, expected.length, 'should be the same length.');
-            // The "fail" lines in log.js should NOT be output!
-            test.ok(actual.indexOf('fail') === -1, 'should not output after exit is called.');
             test.done();
           });
         };

test/fixtures/log-broken.js

@@ -18,6 +18,3 @@ for (var i = 0; i < max; i++) {
 }
 
 process.exit(errorCode);
-
-stdout('fail');
-stderr('fail');

test/fixtures/log.js

@@ -20,6 +20,3 @@ for (var i = 0; i < max; i++) {
 }
 
 exit(errorCode);
-
-stdout('fail');
-stderr('fail');