Open thlorenz opened 11 years ago
@toots Any chance of getting this fixed? I'm currently having to manually change Buffer.isBuffer() to use util.isBuffer()'s logic (similar to @thlorenz's workaround) because require('stream').Readable uses Buffer.isBuffer() in chunkInvalid() and that always fails with the current Buffer.isBuffer() implementation.
Hi guys. Unfortunately, I don't have a lot of time to investigate this at the moment. I'd be happy to consider a PR, although I am concerned as to why buf instanceof Buffer
isn't returning the expected value. Maybe there's something more important going on here..
I think this may be related to substack/node-browserify#513 in which two copies of Buffer are injected into bundles.
I ran into this while writing a browser side Writable Stream. The problem is basically that
Buffer.isBuffer(buf)
returnsfalse
although it is one. This is due tobuf instanceof Buffer
returningfalse
-- I tried this in the browser console as well.I commented on my workaround here.
You could use this project as a test bed, i.e.:
You should then be able to debug into
d3-gauge-writable
assuming you enabled source maps on your browser.