All Versions
35
Latest Version
Avg Release Cycle
93 days
Latest Release
1727 days ago
Changelog History
Page 3
Changelog History
Page 3
-
v2.10.2 Changes
๐ Bugfix
- Uncaught errors from promise-back streams weren't being correctly logged in certain circumstances when using a Promise implementation that does not log unhandled promise exceptions. All uncaught highland errors should now be correctly logged. #591. Fixes #589.
- ๐ Users using bluebird as their Promise implementation may have seen an error that says "a promise was created in a handler at ... but was not returned from it". This is a false positive, and Highland's use of promises have been updated to suppress this warning. #588.
-
v2.10.0 Changes
๐ New additions
of
: Creates a stream that sends a single value then ends. #520.fromError
: Creates a stream that sends a single error then ends. #520.- When constructing a Highland stream from a Node Readable, the
onFinish
handler may now turn off the default automatic end on errors behavior by returning an object with the propertycontinueOnError
set totrue
. #534. Fixes #532.
-
v2.8.1 Changes
๐ Bugfix
- The
Readable
stream wrapper changes from2.8.0
assumed thatclose
would never be emitted beforeend
for any stream. This is not the case forSockets
, which willclose
when the client disconnects but willend
only when it has piped all of its data. For a slow consumer,end
may happen afterclose
, causing the Highland stream to drop all data afterclose
is emitted.
This release fixes the regression at the cost of restoring the old behavior of never ending the Stream when only
close
is emitted. This does not affect the case whereerror
events are emitted withoutend
. That still works fine. To manually end a stream when it emitsclose
, listen to the event and callstream.end()
. Fixes #490. - The
-
v2.8.0 Changes
๐ Bugfix
- A Highland Stream that wraps
Readable
now properly handles the case where theReadable
emits theclose
event but not theend
event (this can happen with anfs
read stream when it encounters an error). It will also end the wrapper stream when it encounters an error (this happens when reading from a non-existent file). Before, such streams would simply never end. #479. Fixes #478.
๐ New additions
toCallback
: method for returning the result of a stream to a nodejs-style callback function. #493. Fixes #484.
๐ Improvements
- A Highland Stream that wraps
-
v2.7.3 Changes
๐ Bugfix
pipe
now properly unbinds itsdrain
handler from the destination when it is done. Previously, there would have been a memory leak if the destination is long-lived (e.g., as withprocess.stdout
). #466.