-
Notifications
You must be signed in to change notification settings - Fork 7.3k
docs: missing prefinish
writable stream event
#8767
Comments
Are you able to share this code with us, or at least the relevant part? |
Sure, it's here. Without the To reproduce, comment out the I don't have time at the moment to create a minimal test case for this, but it seems the change was introduced in c38ce9bc0a. |
I couldn't run Nonetheless, I investigated why the Thank you! |
It's not that it isn't emitting Sorry about the lack of instructions. You should just need to checkout the rewrite branch and then do |
Sorry, I had read your second comment only and lost the context. I'll take another look later, thank you for the instructions on how to install ssh2-streams. |
@mscdex ... still something you'd like to see? have time to do a PR? |
@jasnell Yes, it is still something I'd like to see. However I don't know the reasons for the change in behavior and all that, so I'm probably not the best one to write documentation for it. |
@chrisdickinson @trevnorris ... are either of you able to clarify the change that was made here? |
This bit me tonight. I had a script that worked fine in node 0.10.33 but 0.11.14 was calling
finish
on next tick or later, causing unexpected behavior. After diving into the code I found that there is now also aprefinish
event that I now listen on for node 0.11+.It seems like if backwards compatibility can't be kept here, that
prefinish
should at least be publicly documented along with information comparing it tofinish
and how it all deviates from node 0.10 behavior.The text was updated successfully, but these errors were encountered: