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.137.185.239
Domains :
Cant Read [ /etc/named.conf ]
User : web
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
home /
www /
wb /
node_modules /
stream-exhaust /
Delete
Unzip
Name
Size
Permission
Date
Action
README.md
1.01
KB
-rw-rw-r--
2022-08-30 11:49
index.js
550
B
-rw-rw-r--
2022-08-30 11:49
package.json
641
B
-rw-rw-r--
2022-08-30 11:49
test.js
4.14
KB
-rw-rw-r--
2022-08-30 11:49
Save
Rename
# stream-exhaust Ensure that the provided stream is flowing data, even if the stream hasn't been piped to another stream. ```javascript var exhaustively = require('stream-exhaust'); exhaustively(fs.createReadStream(__filename)) .on('close', () => { console.log('all done, despite being streams{1+N}!') }); ``` ## Prior Art This is based on [stream-consume](https://github.com/aroneous/stream-consume) by [aroneous](https://github.com/aroneous). It is a separate package because it has different semantics: 1. It does not call `.resume()` on streams2+ streams. streams2 streams monkeypatch `.pipe` when entering flowing mode; avoiding `resume()` avoids that fate. 2. It does not examine `._readableState`; instead it checks for the presence of `._read`. ## API ### exhaust(Stream s) -> Stream s Takes a stream, `s`, and returns it. Ensures that the stream is flowing, either by calling `.resume()` if the stream is a streams1 stream, or by piping it to a "black hole" stream that continually asks for more data. ## License MIT