You Have To Explicitly End Streams After Pipes Break In Node.js

added by JavaScript Kicks
10/6/2014 2:24:34 PM

92 Views

I've spent the last few months learning about Node.js in an effort to figure out why my Gulp.js script doesn't work (I still don't know). This has become quite the Herculean task, winding my way down the rabbit hole of Node.js streams. This morning, I wanted to look at one interesting behavior - the fact that you have to explicitly end your streams after your pipes break.


1 comments

Robert Greyling
10/6/2014 8:44:12 PM
Streams aren't the only things that feel broken in Node without actually being broken. This is just one of the big learning curve ticket items when working with Node. Great explanation in this post however, make it very clear once you know what to look for