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
Currently in order to know that streams passed to multipipe have been processed callback should be passed. It could be useful if close event will be emitted (only once of course) on a result stream at the end of processing. According to nodejs docs close event is optional for readable and writeable streams so that should not be a breaking change for current multipipe api.
The text was updated successfully, but these errors were encountered:
Hi, there.
Currently in order to know that streams passed to multipipe have been processed callback should be passed. It could be useful if
close
event will be emitted (only once of course) on a result stream at the end of processing. According to nodejs docsclose
event is optional for readable and writeable streams so that should not be a breaking change for current multipipe api.The text was updated successfully, but these errors were encountered: