2 known bugs in readable-stream, with affected versions, fixes and workarounds. Sourced from upstream issue trackers.
| Severity | Affected | Fixed in | Title | Status | Source |
|---|---|---|---|---|---|
| medium | any | \u2014 | Add a browser polyfill for `process.emitWarning` > In the browser process.emitWarning is undefined (not a function)
From @jimmywarting
https://github.com/nodejs/readable-stream/commit/e9cde33830a2ee06311f4a7b03d0656720301e4b#r30408314
| fixed | github:361 |
| medium |
Get this data programmatically \u2014 free, no authentication.
curl https://depscope.dev/api/bugs/npm/readable-stream| \u2014 |
`Readable.fromWeb` and `Readable.toWeb` do not seems to be properly implemented First, thank you for your amazing work on `readable-stream`!
`Readable.fromWeb` an `Readable.toWeb` are calling the [`newStreamReadableFromReadableStream`](https://github.com/nodejs/readable-stream/blob/81c52641299e5ea3a5e37179967bb13691cad081/lib/internal/streams/readable.js#L1289) and [`newReadableStreamFromStreamReadable`](https://github.com/nodejs/readable-stream/blob/81c52641299e5ea3a5e37179967bb13691cad081/lib/internal/streams/readable.js#L1293) functions on the `webStreamsAdapters`.
However `webStreamsAdapters` [is only defined as an empty object](https://github.com/nodejs/readable-stream/blob/81c52641299e5ea3a5e37179967bb13691cad081/lib/internal/streams/readable.js#L1284) leading to a failure.
The same problem seems to affect `Writable` and `Duplex`. |
| fixed |
| github:482 |