[stream] Standardize a way for writable streams to do work after all data has been consumed.

@TomFrost

There was a lot of discussion about this pre-fork:

Note that while waiting for an upstreaming fix, @TomFrost implemented a workaround that is published on npmjs.org:

Perhaps it will be helpful in considering the issue.

@Fishrock123

@Fishrock123 I opened an issue in the readable-stream queue as you suggested:

If this is the wrong place for stream issues now, this can be closed.

I'm +1. Also want _open and _close hooks for all streams

@vkurchatkin

+1 from me also.

@vkurchatkin What do you mean by _open and _close. Are you referring to fs streams which does fs.open?

Yeah, default open, close and destroy implementations which call hooks. Also auto-open, like in fs

Redirecting conversation to the readable-stream issue.

Navigation Menu