es.split breaks pipe chain?

[kevzettler]

I have a custom stream that looks like this

function QueryFormatStream(){}
util.inherits(QueryFormatStream, Stream);

QueryFormatStream.prototype.write = function(query){
  console.log("we got query", query);
  this.emit('data', query);
};

QueryFormatStream.prototype.end = function(){
  this.emit('end');
};

module.exports = QueryFormatStream;

I have a pipe chain that looks like:

  var stream = fs.createReadStream(file_path)
                 .pipe(zlib.createGunzip())
                 .pipe(es.split())
                 .pipe(new QueryFormatStream())
                 .pipe(process.stdout)

running the stream like this produces no output and the console log statement in QueryFormatStream never gets called.

However calling it like so, without the QueryFormatStream correctly pipes it to process.stdout

  var stream = fs.createReadStream(file_path)
                 .pipe(zlib.createGunzip())
                 .pipe(es.split())
                 .pipe(process.stdout)

[dominictarr]

That is not the right way to create a stream. If you are making a classic stream you also need to set
readable and writable properties (see the node docs) but simplest is just to use my through module or rvagg's through2.