Michał Dzienisiewicz
Results
6
comments of
Michał Dzienisiewicz
I can confirm that upgrading Chrome from v104 to v105 has exposed the same behavior.
Any update on this?
@bnoordhuis ```javascript // since it's ESM, save it as .mjs import fs from 'node:fs' import process from 'node:process' import {Readable} from 'node:stream' // we initialize a stream, but not start...
@debadree25 Sounds like a workaround that is good enough for me, thanks!
In meanwhile I found another workaround - `ReadableStream.from(randomNodeStream)` seems to do the job just right, without having to set the queueing strategy explicitly.
We have tested 10.3.0 and 10.5.0 on Node 21.7.3 & MacOS Sonoma and unfortunately the problem is still there.