A replacement for process.exit that ensures stdio are fully drained before exiting. 

cowboy

exit

module.exports = function exit(exitCode, streams) {

  if (!streams) { streams = [process.stdout, process.stderr]; }

  // Actually exit if all streams are drained.

    // Count drained streams now, but monitor non-drained streams.

      stream.write('', 'utf-8', function() {

  // If all streams were already drained, exit now.

  // In Windows, when run as a Node.js child process, a script utilizing

  // this library might just exit with a 0 exit code, regardless. This code,

  // despite the fact that it looks a bit crazy, appears to fix that.

  "description": "A replacement for process.exit that ensures stdio are fully drained before exiting.",

  "homepage": "https://github.com/cowboy/node-exit",

    "url": "git://github.com/cowboy/node-exit.git"

    "url": "https://github.com/cowboy/node-exit/issues"

      "url": "https://github.com/cowboy/node-exit/blob/master/LICENSE-MIT"

# exit [![Build Status](https://secure.travis-ci.org/cowboy/node-exit.png?branch=master)](http://travis-ci.org/cowboy/node-exit)

To make a long story short, if `process.exit` is called on Windows, script output is often truncated when pipe-redirecting `stdout` or `stderr`. This module attempts to work around this issue by waiting until those streams have been completely drained before actually calling `process.exit`.

See [Node.js issue #3584](https://github.com/joyent/node/issues/3584) for further reference.

Tested in OS X 10.8, Windows 7 on Node.js 0.8.25 and 0.10.18.

Based on some code by [@vladikoff](https://github.com/vladikoff).

Install the module with: `npm install exit`

// These lines should appear in the output, EVEN ON WINDOWS.

// These lines shouldn't appear in the output.

## Don't believe me? Try it for yourself.

In Windows, clone the repo and cd to the `test\fixtures` directory. The only difference between [log.js](test/fixtures/log.js) and [log-broken.js](test/fixtures/log-broken.js) is that the former uses `exit` while the latter calls `process.exit` directly.

This test was done using cmd.exe, but you can see the same results using `| grep "std"` in either PowerShell or git-bash.

C:\node-exit\test\fixtures>node log.js 0 10 stdout stderr 2>&1 | find "std"

C:\node-exit\test\fixtures>node log-broken.js 0 10 stdout stderr 2>&1 | find "std"

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using [Grunt](http://gruntjs.com/).

2013-11-26 - v0.1.2 - Fixed a bug with hanging processes.  

2013-09-26 - v0.1.1 - Fixed some bugs. It seems to actually work now!  

		@@ -21,4 +21,2 @@ /*
		streams.forEach(function(stream) {
		// Prevent further writing.
		stream.write = function() {};
		// Count drained streams now, but monitor non-drained streams.
		@@ -28,3 +26,3 @@ if (stream.bufferSize === 0) {
		} else {
		stream.once('drain', function() {
		stream.write('', 'utf-8', function() {
		drainCount++;
		@@ -34,2 +32,4 @@ tryToExit();
		}
		// Prevent further writing.
		stream.write = function() {};
		});
		@@ -36,0 +36,0 @@ // If all streams were already drained, exit now.

		{
		"name": "exit",
		"description": "A replacement for process.exit that ensures stdio are fully drained before exiting.",
		"version": "0.1.1",
		"version": "0.1.2",
		"homepage": "https://github.com/cowboy/node-exit",
		@@ -6,0 +6,0 @@ "author": {

		@@ -69,2 +69,3 @@ # exit [![Build Status](https://secure.travis-ci.org/cowboy/node-exit.png?branch=master)](http://travis-ci.org/cowboy/node-exit)
		## Release History
		2013-11-26 - v0.1.2 - Fixed a bug with hanging processes.
		2013-09-26 - v0.1.1 - Fixed some bugs. It seems to actually work now!
		@@ -71,0 +72,0 @@ 2013-09-20 - v0.1.0 - Initial release.

Improved metrics