Commander.js: Support piping

[mathiasbynens]

Say you want to support piping in your script, e.g.:

echo "foo bar" | ./test.js

That’s currently possible using code that looks like this:

var data = '';
function withPipe(data) {
   console.log('content was piped');
   console.log(data.trim());
}
function withoutPipe() {
   console.log('no content was piped');
}

var self = process.stdin;
self.on('readable', function() {
    var chunk = this.read();
    if (chunk === null) {
        withoutPipe();
    } else {
       data += chunk;
    }
});
self.on('end', function() {
   withPipe(data);
});

It would be neat if commander.js could somehow abstract all this away and make it easier to write scripts that accept piped content.

[jrschumacher]

:+1:

This is what I did:

//...
var stdin = '';

program
  .command('some-command [message]')
  .action(function(message) {
    if(stdin) {
      message = stdin;
    }
  });

if(process.stdin.isTTY) {
  program.parse(process.argv);
}
else {
  process.stdin.on('readable', function() {
      var chunk = this.read();
      if (chunk !== null) {
         stdin += chunk;
      }
  });
  process.stdin.on('end', function() {
    program.parse(process.argv); 
  });
}

[Potherca]

I did the same thing here. Works like a charm.

[shadowspawn]

Popular approach from @jrschumacher , thanks

This issue has not had any activity in over six months. It isn't likely to get acted on due to this report.

Feel free to open a new issue if it comes up again, with new information and renewed interest.

Thank you for your contributions.