All Versions
35
Latest Version
Avg Release Cycle
93 days
Latest Release
1050 days ago

Changelog History
Page 2

  • v2.13.3 Changes

    February 20, 2019

    ๐Ÿ›  Bugfix

    • ๐Ÿ›  Fixes a bug in pipe where errors would be emitted twice.
  • v2.13.2 Changes

    February 20, 2019

    ๐Ÿ›  Bugfix

    • ๐Ÿ›  Fixes a regression in the through transform. If it is called with an un-paused through stream and the source Highland stream has buffered data (or generates data synchronously), then that data may be lost. #671.
    • ๐Ÿ›  Fix pipe so that it does not emit data synchronously. This allows for chained pipes to work properly even if a stream in the middle of the pipe is unpaused. #671.
  • v2.13.1 Changes

    February 15, 2019

    ๐Ÿ›  Bugfix

    • ๐Ÿ›  Fixes a potential deadlock when wrapping node Readables in node 10+. #670.
  • v2.13.0 Changes

    March 21, 2018

    ๐Ÿ†• New additions

    • isNil: Returns true if the argument is the end of stream marker. This can be useful as a user-defined type guard in Typescript. #645
  • v2.12.0 Changes

    ๐Ÿ†• New additions

    • toNodeStream: Returns a native node Readable #644
  • v2.11.1 Changes

    ๐Ÿ›  Bugfix

    • โœ‚ Remove usages of Function.prototype.bind. We support IE8. #632.
    • โž• Add a section about supported JS engines to the documentation.
  • v2.11.0 Changes

    ๐Ÿ†• New additions

    • toPromise: Converts a one-element or zero-element stream to a Promise given a Promise/A+ compliant promise constructor. #628. Fixes #627.
  • v2.10.5 Changes

    ๐Ÿ›  Bugfix

    • ๐Ÿšš Streams constructed from an EventEmitter or jQuery element will now remove itself when the stream is destroyed. Fixes #500. #609.
  • v2.10.4 Changes

    ๐Ÿ›  Bugfix

    • Same as 2.10.3 but with a more conservative fix to minimize the risk of regressions.
  • v2.10.3 Changes

    ๐Ÿ›  Bugfix

    • In certain cases, consuming a stream that has been resumed may cause a stream generator/consume handler to be called twice without next() ever being called. This is mostly relevant for .each(...).done(...) use cases. Noticed in #570 (comment). #608.