You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no way to detect that stream.pipe is finished. There is an event finish for writable streams, but it is unusable for specific usecases (writing to process.stdout or process.stderr).
And if I understand it correctly, finish event is not emitted when pipe is called with {end: false}. So I can not simply pipe multiple read streams to the single write stream.
The text was updated successfully, but these errors were encountered:
Seems like this has been addressed by the OP but if not, please feel free to re-open. Not sure this would get back-ported to v6.x, if it hasn't been already.
There is no way to detect that
stream.pipe
is finished. There is an eventfinish
for writable streams, but it is unusable for specific usecases (writing toprocess.stdout
orprocess.stderr
).And if I understand it correctly,
finish
event is not emitted whenpipe
is called with{end: false}
. So I can not simply pipe multiple read streams to the single write stream.The text was updated successfully, but these errors were encountered: