Nate Fischer

I think the best approach is to implement this as an attribute on plugins/commands. This will also expose one way for plugin authors to deprecate their plugins. The deprecation message...

No deprecated commands yet, so I'm bumping this back a milestone.

Let's put some more thought into solving this. I'd like to implement this with [util.deprecate()](https://nodejs.org/api/util.html#util_util_deprecate_function_string) if possible. We should use care that `--trace-deprecation` and `--throw-deprecation` give meaningful stack traces, which...

@freitagbr can you take this? It'd be good to have this finished shortly after #866. --- Removing the "breaking" label because this issue is about support for deprecating plugins, this...

Yes, that's a great test case for this. You're absolutely correct, it has to do with how our pipes are designed. The [API](https://github.com/shelljs/shelljs/blob/master/src/common.js#L370) just returns a string value, empty or...

Another possibility is to throw an exception if there is no piped input. Hmmm... not sure what the correct behavior should be. Either way, I'm going to triage this for...

> I should probably open more issues if I find time later ;-)) Helpful issues are always appreciated. Streaming might be hard to support without breaking compatibility with previous versions...

I'll see if I can actually write up a fix for this during the week

Bumping to v0.9 milestone

Hi @scott113341. Thanks for taking a look into this. The extra newline was intended. Here's an example of why it works this way: Using [n_shell](https://github.com/nfischer/n_shell): ``` javascript $ n_shell shelljs...