Broken on 0.8 and 0.9 about gulp HOT 4 CLOSED

I'll take a look.

from gulp.

It appears Orchestrator is uninvolved. When the input file is streamed (buffer:false) I can't get stream data from file.contents.on('data', or file.contents.on('end', in outstream (/test/dest.js line 80). If buffer:true it works just fine (but it's also no longer an inner-stream.) I can get data if I build an intermediate stream. instream.pipe(es.map(function (file, cb) { file.contents.once('end',... works just fine, but hook it onto outstream and no go. Even doodling through writeFile, streamFile, createOutputStream, etc, I get the same: can't get any data out of file.contents once the data reaches createOutputStream. Could this be a streams vs. streams2 thing? Maybe related to nodejs/readable-stream#69? Perhaps we just note that buffer:false isn't supported in Node v0.8? (It wasn't supported at all until very recently.)

from gulp.

Ah yeah thats a 0.8 streaming thing. >=0.9 won't start emitting data until something is listening. In 0.8 it fires all of the data out before anything is attached. We can optionally .pause() on it on 0.8 and have a note that says they need to call .resume() when they need the data

from gulp.

Fixed in the latest version

from gulp.