All Versions
35
Latest Version
Avg Release Cycle
93 days
Latest Release
1981 days ago
Changelog History
Page 1
Changelog History
Page 1
-
v3.0.0 Changes
July 07, 20192019-02-20
-
v3.0.0-beta.9 Changes
February 20, 2019๐ This release contains all changes from 2.13.3.
-
v3.0.0-beta.8 Changes
February 15, 2019๐ This release contains all changes from 2.13.1.
-
v3.0.0-beta.7 Changes
November 01, 2018๐ New additions
ap
- Applies a stream of function(s) to the stream of value(s). #643.empty
- Creates an empty stream. #657.- Implements the Fantasy Land Alternative, Filterable, and Monad specifications. #658.
๐ Bugfix
-
v3.0.0-beta.6 Changes
๐ This release contains all changes from 2.12.0.
๐ฅ Breaking changes
toNodeStream
- In 2.x, if you calltoNodeStream
on a Highland stream that emits objects without setting{objectMode: true}
, the resultingReadable
may simply ignore any objects that are emitted (depending on the implementation ofStringDecoder
). In 3.x, theReadable
will always emit an error.
Also, in 2.x, calling
toNodeStream
will immediately consume the source. In 3.x, the source stream will only be consumed when theReadable
is consumed.Other
- ๐
stopOnError
- updatestopOnError
documentation to includepush
#650.
-
v3.0.0-beta.5 Changes
๐ฅ Breaking changes
stream.source
- The (undocumented)source
property on a stream no longer exists.consume
- It is no longer possible toconsume
the same stream multiple times, even after the originalconsume
has pushednil
. Attempting to do so will result in an error. This affects all transforms that are implemented viaconsume
.- Old Behavior: Code like this used to work
javascript const stream = _([1, 2, 3]); stream.take(1) .toArray(array => { console.log(array); // => [1] stream.take(1).toArray(array2 => { console.log(array2); // => [2] stream.take(1).toArray(array3 => { console.log(array3); // => [3] }); }); });
- New Behavior:
javascript const stream = _([1, 2, 3]); stream.take(1) .toArray(array => { console.log(array); // => [1] stream.take(1); // The call to take(1) will fail. });
- Old Behavior: Code like this used to work
drop
#559 Fixes #594- Old Behavior: if
n
isn't a number or is negative, it defaults to0
. - New Behavior: if
n
is not a number or if it is negative, an error is thrown.
- Old Behavior: if
fork
- It is no longer possible to callfork
after a call toconsume
on the same stream. Attempting to do so will result in an error. This also applies to all transforms. Note that each transform returns a new stream, so it is still possible to fork a stream that has been transformed.- Code like this used to work:
javascript const stream = _([1, 2, 3]).map(x => x + 1); const fork1 = stream.map(x => x * 2); // stream is consumed. const fork2 = stream.fork().map(x => x * 3); // then forked. // fork1 and fork2 share backpressure.
In 3.0.0, this code should be written asjavascript const stream = _([1, 2, 3]).map(x => x + 1); const fork1 = stream.fork().map(x => x * 2); // stream must be explicitly forked const fork2 = stream.fork().map(x => x * 3);
- Code like this used to work:
map
- Passing a non-function value tomap
now throws an error.- Old Behavior - Passing a non-function value to
map
caused it to map all stream values to the passed in value.
- Old Behavior - Passing a non-function value to
reduce
- The order of the arguments toreduce
has been swapped.- Old Behavior:
stream.reduce(memo, reducer)
- New Behavior:
stream.reduce(reducer, memo)
- Old Behavior:
scan
- The order of the arguments toscan
has been swapped.- Old Behavior:
stream.scan(memo, reducer)
- New Behavior:
stream.scan(reducer, memo)
- Old Behavior:
slice
#559 Fixes #594- Old Behavior: if
start
isn't a number, it defaults to0
, and ifend
isn't a number, it defaults toInfinity
. Ifstart
orend
are negative, they are treated as if they are0
instead. - New Behavior: if
start
orend
are not numbers or if they are negative, an error is thrown.start
andend
are optional and default to0
andInfinity
, respectively.
- Old Behavior: if
take
#559 Fixes #594- Old Behavior: if
n
isn't a number, it defaults toInfinity
. Ifn
is negative, it is treated as if it is0
. - New Behavior: if
n
is not a number or if it is negative, an error is thrown.
- Old Behavior: if
zipAll
-zipAll
has been renamedzipEach
.zipAll0
-zipAll0
has been renamedzipAll
.
๐ New additions
-
v3.0.0-beta.11 Changes
๐ Bugfix
- ๐
fork
- Updates the documentation forfork
to match the better version from 2.x.
- ๐
-
v3.0.0-beta.10 Changes
July 07, 2019๐ New additions
takeWhile
- returns a new stream that ends when the function passed as a parameter stops returning true. #677.- ๐ Async Iterator/Iterable support - Async iterators and iterables (as defined by the Async Iteration specs), can now be passed to the Highland constructor function. #682.
-
v2.13.5
July 31, 2019 -
v2.13.4
April 05, 2019