Gecko [ unitednationsplay.com ]

Linux unitednationsplay.com 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
nginx/1.20.1
Server IP : 188.130.139.92 & Your IP : 3.141.164.253
Domains : Cant Read [ /etc/named.conf ]
User : web

Name	Size	Permission	Date
test	[ DIR ]	drwxr-xr-x	2021-02-04 21:24
.travis.yml	68 B	-rw-r--r--	1985-10-26 08:15
LICENSE	1.03 KB	-rw-r--r--	1985-10-26 08:15
README.md	1009 B	-rw-r--r--	1985-10-26 08:15
index.js	981 B	-rw-r--r--	1985-10-26 08:15
package.json	1.28 KB	-rw-r--r--	2021-02-04 21:24

Rename

# stdout-stream

Non-blocking stdout stream

npm install stdout-stream

[![build status](http://img.shields.io/travis/mafintosh/level-filesystem.svg?style=flat)](http://travis-ci.org/mafintosh/stdout-stream)
![dat](http://img.shields.io/badge/Development%20sponsored%20by-dat-green.svg?style=flat)

## Rant

Try saving this example as `example.js`

``` js
console.error('start');
process.stdout.write(new Buffer(1024*1024));
console.error('end');
```

And run the following program

```
node example.js | sleep 1000
```

The program will never print `end` since stdout in node currently is blocking - even when its being piped (!).

stdout-stream tries to fix this by being a stream that writes to stdout but never blocks

## Usage

``` js
var stdout = require('stdout-stream');

stdout.write('hello\n'); // write should NEVER block
stdout.write('non-blocking\n')
stdout.write('world\n');
```

`stdout-stream` should behave in the same way as `process.stdout` (i.e. do not end on pipe etc)

## License

MIT