You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

58 lines
2.9 KiB

4 years ago
  1. # readable-stream
  2. ***Node-core v8.11.1 streams for userland*** [![Build Status](https://travis-ci.org/nodejs/readable-stream.svg?branch=master)](https://travis-ci.org/nodejs/readable-stream)
  3. [![NPM](https://nodei.co/npm/readable-stream.png?downloads=true&downloadRank=true)](https://nodei.co/npm/readable-stream/)
  4. [![NPM](https://nodei.co/npm-dl/readable-stream.png?&months=6&height=3)](https://nodei.co/npm/readable-stream/)
  5. [![Sauce Test Status](https://saucelabs.com/browser-matrix/readable-stream.svg)](https://saucelabs.com/u/readable-stream)
  6. ```bash
  7. npm install --save readable-stream
  8. ```
  9. ***Node-core streams for userland***
  10. This package is a mirror of the Streams2 and Streams3 implementations in
  11. Node-core.
  12. Full documentation may be found on the [Node.js website](https://nodejs.org/dist/v8.11.1/docs/api/stream.html).
  13. If you want to guarantee a stable streams base, regardless of what version of
  14. Node you, or the users of your libraries are using, use **readable-stream** *only* and avoid the *"stream"* module in Node-core, for background see [this blogpost](http://r.va.gg/2014/06/why-i-dont-use-nodes-core-stream-module.html).
  15. As of version 2.0.0 **readable-stream** uses semantic versioning.
  16. # Streams Working Group
  17. `readable-stream` is maintained by the Streams Working Group, which
  18. oversees the development and maintenance of the Streams API within
  19. Node.js. The responsibilities of the Streams Working Group include:
  20. * Addressing stream issues on the Node.js issue tracker.
  21. * Authoring and editing stream documentation within the Node.js project.
  22. * Reviewing changes to stream subclasses within the Node.js project.
  23. * Redirecting changes to streams from the Node.js project to this
  24. project.
  25. * Assisting in the implementation of stream providers within Node.js.
  26. * Recommending versions of `readable-stream` to be included in Node.js.
  27. * Messaging about the future of streams to give the community advance
  28. notice of changes.
  29. <a name="members"></a>
  30. ## Team Members
  31. * **Chris Dickinson** ([@chrisdickinson](https://github.com/chrisdickinson)) &lt;christopher.s.dickinson@gmail.com&gt;
  32. - Release GPG key: 9554F04D7259F04124DE6B476D5A82AC7E37093B
  33. * **Calvin Metcalf** ([@calvinmetcalf](https://github.com/calvinmetcalf)) &lt;calvin.metcalf@gmail.com&gt;
  34. - Release GPG key: F3EF5F62A87FC27A22E643F714CE4FF5015AA242
  35. * **Rod Vagg** ([@rvagg](https://github.com/rvagg)) &lt;rod@vagg.org&gt;
  36. - Release GPG key: DD8F2338BAE7501E3DD5AC78C273792F7D83545D
  37. * **Sam Newman** ([@sonewman](https://github.com/sonewman)) &lt;newmansam@outlook.com&gt;
  38. * **Mathias Buus** ([@mafintosh](https://github.com/mafintosh)) &lt;mathiasbuus@gmail.com&gt;
  39. * **Domenic Denicola** ([@domenic](https://github.com/domenic)) &lt;d@domenic.me&gt;
  40. * **Matteo Collina** ([@mcollina](https://github.com/mcollina)) &lt;matteo.collina@gmail.com&gt;
  41. - Release GPG key: 3ABC01543F22DD2239285CDD818674489FBC127E
  42. * **Irina Shestak** ([@lrlna](https://github.com/lrlna)) &lt;shestak.irina@gmail.com&gt;