alfie
/
invoicer
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
dev
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
invoicer/node_modules/readable-stream
History
alfiepates b0b64a865d initial dev commit. everything is broken. 8 years ago
..
lib initial dev commit. everything is broken. 8 years ago
.npmignore initial dev commit. everything is broken. 8 years ago
LICENSE initial dev commit. everything is broken. 8 years ago
README.md initial dev commit. everything is broken. 8 years ago
duplex.js initial dev commit. everything is broken. 8 years ago
float.patch initial dev commit. everything is broken. 8 years ago
package.json initial dev commit. everything is broken. 8 years ago
passthrough.js initial dev commit. everything is broken. 8 years ago
readable.js initial dev commit. everything is broken. 8 years ago
transform.js initial dev commit. everything is broken. 8 years ago
writable.js initial dev commit. everything is broken. 8 years ago

README.md
Unescape Escape

readable-stream

Node-core streams for userland

NPM NPM

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

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.

readable-stream comes in two major versions, v1.0.x and v1.1.x. The former tracks the Streams2 implementation in Node 0.10, including bug-fixes and minor improvements as they are added. The latter tracks Streams3 as it develops in Node 0.11; we will likely see a v1.2.x branch for Node 0.12.

readable-stream uses proper patch-level versioning so if you pin to "~1.0.0" you’ll get the latest Node 0.10 Streams2 implementation, including any fixes and minor non-breaking improvements. The patch-level versions of 1.0.x and 1.1.x should mirror the patch-level versions of Node-core releases. You should prefer the 1.0.x releases for now and when you’re ready to start using Streams3, pin to "~1.1.0"