Blame view

node_modules/stdout-stream/README.md 1009 Bytes
2a09d1a4   liuqimichale   添加宜春 天水 宣化
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
  # 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