Releases: nodejs/readable-stream
fix browserify build
fix for v2.1.1 which forgot to remove the browserify section of the package.json after the dependencies were removed, unclear how this passed our tests which use browserify. ht @ahutchings
remove unneded browserify transforms
It turns out there was a way to do the environmental variable from v2.1.0 without including 2 megs of browserify transforms, ht @sindresorhus
Add enviromental variable to allow smoke testing
running in node with the environmental variable READABLE_STRAM
set to 'disable' will cause this module to simply return the platform streams. The goal of this is to allow us to test changes to node streams and see if they will break modules using readable-stream. Transforms have been added so that in browserify (where the streams module is build on readable-streams) this change will be removed and not bloat the build.
backport of v2.1.0 to the ~1.1.0 line
back port of v2.1.0 to the ~1.1.0 line, doesn't include the transform changes because browserify streams are unconditionally imported in that version.
Back port of v2.1.0 to the ~1.0.0 line
back port of v2.1.0 to the ~1.0.0 line, doesn't include the transform changes because browserify streams are unconditionally imported in that version.
v2.0.6 based on node v5.8.0
User facing change are
- nodejs/node#4354 which is a perf improvement when sending a lot of small chunks
- #188 which fixes sync writes causing a stack overflow in node 0.10 (with zero overhead for non node 0.10)
Behind the scenes we are now using babel to deal with the es6 features such as let, const, and arrow functions so those should be a lot cleaner now