juliangruber: readable should be listening to 'finish' itself and cleaning up, I think the fact that read() keeps on returning available stuff on read(n) means sends the signal that it's not finished, hence the need to finish it manually

juliangruber: but you can imagine a use-case here, a readable that keeps on reading, pipe it to an endpoint until that endpoint has had enough, unpipe and pipe it to another endpoint and the buffer stays intact

Raynos: and what happens when npm dedupes and some patch levels mispatch and now some dep lower in the tree doesn't work with the version that exists higher up but you want to use the higher up version for your stuff?