Skip to content

No suitable finish event for pipe #17037

Description

@polomsky
  • Version: 8.7.0
  • Platform: linux
  • Subsystem: stream

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.

Activity

added
questionIssues asking questions about Node.js.
on Nov 15, 2017

polomsky commented on Nov 21, 2017

@polomsky
Author

After investigation I have found that event unpipe can be probably used for that purpose. Sadly it is not in the 6.x version. Fixed by #11876

apapirovski commented on Apr 12, 2018

@apapirovski
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionIssues asking questions about Node.js.streamIssues and PRs related to Node.js streams.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions