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.
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.
Activity
polomsky commentedon Nov 21, 2017
After investigation I have found that event
unpipecan be probably used for that purpose. Sadly it is not in the 6.x version. Fixed by #11876apapirovski commentedon Apr 12, 2018
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.