hangar-tech/biofriction-wp-theme
hangar-tech
/
biofriction-wp-theme
3
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
biofriction-wp-theme/node_modules/readable-stream
History
jorge a7910c81a8 moved to new repo 2021-10-26 14:18:09 +02:00
..
doc/wg-meetings moved to new repo 2021-10-26 14:18:09 +02:00
lib moved to new repo 2021-10-26 14:18:09 +02:00
.npmignore moved to new repo 2021-10-26 14:18:09 +02:00
.travis.yml moved to new repo 2021-10-26 14:18:09 +02:00
CONTRIBUTING.md moved to new repo 2021-10-26 14:18:09 +02:00
GOVERNANCE.md moved to new repo 2021-10-26 14:18:09 +02:00
LICENSE moved to new repo 2021-10-26 14:18:09 +02:00
README.md moved to new repo 2021-10-26 14:18:09 +02:00
duplex-browser.js moved to new repo 2021-10-26 14:18:09 +02:00
duplex.js moved to new repo 2021-10-26 14:18:09 +02:00
package.json moved to new repo 2021-10-26 14:18:09 +02:00
passthrough.js moved to new repo 2021-10-26 14:18:09 +02:00
readable-browser.js moved to new repo 2021-10-26 14:18:09 +02:00
readable.js moved to new repo 2021-10-26 14:18:09 +02:00
transform.js moved to new repo 2021-10-26 14:18:09 +02:00
writable-browser.js moved to new repo 2021-10-26 14:18:09 +02:00
writable.js moved to new repo 2021-10-26 14:18:09 +02:00

README.md

readable-stream

Node-core v8.1.3 streams for userland Build Status

NPM NPM

Sauce Test Status

npm install --save readable-stream

Node-core streams for userland

This package is a mirror of the Streams2 and Streams3 implementations in Node-core.

Full documentation may be found on the Node.js website.

If you want to guarantee a stable streams base, regardless of what version of 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.

As of version 2.0.0 readable-stream uses semantic versioning.

Streams Working Group

readable-stream is maintained by the Streams Working Group, which oversees the development and maintenance of the Streams API within Node.js. The responsibilities of the Streams Working Group include:

  • Addressing stream issues on the Node.js issue tracker.
  • Authoring and editing stream documentation within the Node.js project.
  • Reviewing changes to stream subclasses within the Node.js project.
  • Redirecting changes to streams from the Node.js project to this project.
  • Assisting in the implementation of stream providers within Node.js.
  • Recommending versions of readable-stream to be included in Node.js.
  • Messaging about the future of streams to give the community advance notice of changes.

Team Members

  • Chris Dickinson (@chrisdickinson) <christopher.s.dickinson@gmail.com>
    • Release GPG key: 9554F04D7259F04124DE6B476D5A82AC7E37093B
  • Calvin Metcalf (@calvinmetcalf) <calvin.metcalf@gmail.com>
    • Release GPG key: F3EF5F62A87FC27A22E643F714CE4FF5015AA242
  • Rod Vagg (@rvagg) <rod@vagg.org>
    • Release GPG key: DD8F2338BAE7501E3DD5AC78C273792F7D83545D
  • Sam Newman (@sonewman) <newmansam@outlook.com>
  • Mathias Buus (@mafintosh) <mathiasbuus@gmail.com>
  • Domenic Denicola (@domenic) <d@domenic.me>
  • Matteo Collina (@mcollina) <matteo.collina@gmail.com>
    • Release GPG key: 3ABC01543F22DD2239285CDD818674489FBC127E