Update deps, add readable-stream

[rvagg]

the main thing here is switching out stream for readable-stream. With Webpack not updating their node-libs-browser we're not getting a newer version of stream-browserify so things break because of breaking changes in readable-stream. So this just bypasses that problem entirely and goes straight to readable-stream which it's using anyway. Also pinning to readable-stream gives some nice stability guarantees.

I'm using this through ripemd160 for btc stuff btw, 👍 on that.

[fanatid]

Thanks. Am I understand correctly, that this can be published as minor version?

[rvagg]

Yep, very safe, readable-stream is the source of the Node core stream package, development happens there and it moves into core. So you get the same version as in the latest Node but you also get it in whatever version of Node you're using when consumed like this. readable-stream is tested back to Node version 6 still too.

[fanatid]

Published as 3.1.0

[danimoh]

Hello @rvagg, I'd be interested in what the breaking changes are that you were talking about and how they affect this library or ripemd160?
I'm currently using this library in a rollup project but encountering problems with circular dependencies.
When using an older version of readable-stream (to be exact when using stream which is then polyfilled for the browser by an older readable-stream version via rollup-plugin-node-polyfills) I'm encountering at least less circular dependencies and can generate code that runs.

[rvagg]

nodejs/readable-stream@c5897e3 this

The removal of the top-level entry points is the main one i keep on hitting. I can't recall if it was coming up here, but probably. Some folks got in the habit of writing things like require('readable-stream/duplex') (or just 'stream/duplex' which worked in the browser at least). I wish those files were just left alone because it's been so disruptive and the Webpack decision to lock readable-stream to v2 has made it harder.

[danimoh]

Alright, thanks for the answer!
I guess in my case I'm then safe for now with still using stream instead of readable-stream.
Hopefully they get the circular dependencies in readable-stream sorted out soon.

[ljharb]

turns out this was a breaking change in that it drops node < 4, which v3.0.0 supports.

[ChALkeR]

@ljharb this was done in #11 before this PR