-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to readable-stream@3 #17
Comments
(Genuinely wondering because this module is 3 years old.) |
readable-stream is not quite the same as the 'stream' module in core. readable-stream does not provide the barebones streams1 API, only streams2+. stream-browserify includes that legacy API. the _ exports are because you can technically do |
i'm working on this for browserify v17 btw, hopefully updating this module this week. |
@goto-bus-stop You're my hero by the way. You've been seriously 🚀 on closing the Gap List |
any update on this..im also facing the same issue. |
Hi, here is a working patch: --- a/index.js
+++ b/index.js
@@ -25,11 +25,11 @@
var inherits = require('inherits');
inherits(Stream, EE);
-Stream.Readable = require('readable-stream/readable.js');
-Stream.Writable = require('readable-stream/writable.js');
-Stream.Duplex = require('readable-stream/duplex.js');
-Stream.Transform = require('readable-stream/transform.js');
-Stream.PassThrough = require('readable-stream/passthrough.js');
+Stream.Readable = require('readable-stream/lib/_stream_readable.js');
+Stream.Writable = require('readable-stream/lib/_stream_writable.js');
+Stream.Duplex = require('readable-stream/lib/_stream_duplex.js');
+Stream.Transform = require('readable-stream/lib/_stream_transform.js');
+Stream.PassThrough = require('readable-stream/lib/_stream_passthrough.js');
// Backwards-compat with node 0.4.x
Stream.Stream = Stream; |
relevant browserify issue browserify/browserify#1880 |
It's holding webpack back at
readable-stream@2
.Also, just genuinely curious... what is this module shimming that isn't provided by
readable-stream
?I noticed this curiosity in
node-libs-browser
(Webpack's native Node shims):Why don't they just use
The text was updated successfully, but these errors were encountered: