z3r0Luck
/
Chat_Room
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Simple Chat Room in NodeJS, expressJS and mongoDB in Docker Swarm
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.
11 Commits
1 Branch
0 Tags
2.5 MiB
 
 
 
 
Tree: b696f530df
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'b696f530df'
${ noResults }
Chat_Room/node_modules/readable-stream
z3r0Luck afad049550
ChatRoom 		4 years ago
..
doc/wg-meetings ChatRoom 4 years ago
lib ChatRoom 4 years ago
.travis.yml ChatRoom 4 years ago
CONTRIBUTING.md ChatRoom 4 years ago
GOVERNANCE.md ChatRoom 4 years ago
LICENSE ChatRoom 4 years ago
README.md ChatRoom 4 years ago
duplex-browser.js ChatRoom 4 years ago
duplex.js ChatRoom 4 years ago
package.json ChatRoom 4 years ago
passthrough.js ChatRoom 4 years ago
readable-browser.js ChatRoom 4 years ago
readable.js ChatRoom 4 years ago
transform.js ChatRoom 4 years ago
writable-browser.js ChatRoom 4 years ago
writable.js ChatRoom 4 years ago

README.md

readable-stream

Node-core v8.11.1 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
  • Irina Shestak (@lrlna) <shestak.irina@gmail.com>