Sindre Sorhus
Sindre Sorhus
Yes! I've always wanted this 😀 That also means you can do use `execa()` with `inherit` and get it written directly console, while still getting the stdout/stderr in the promise.
> Maybe opt-in via an option? 👍 You should make the fake TTY thing in AVA a reusable module we can use here too.
If only Node.js had [`PTY`](https://en.wikipedia.org/wiki/Pseudoterminal) support... _(tl;dr It would let us pretend to be a terminal when spawning a child process)._
> There is pty.js - I've used it before and it works. I'm aware. I've used it too. > It's got a native component though. That's why it's not a...
We could detect the follow custom properties attached to it: ``` path: 'ad', fd: null, flags: 'w', mode: 438, ``` Maybe we should add `isStream.fsWritable()` and `isStream.fsReadable()` methods to [`is-stream`](https://github.com/sindresorhus/is-stream)?
Even better. Less bloat for `is-stream`. The module looks good.
I think we should also at least try to get this into Node.js core by opening an issue argumenting it's the expected behavior.
At least we can then reference Node.js' unwillingness to good UX. It's always worth trying to improve core Node.js if possible, as it benefits of lot more users, and of...
This is becoming more complicated than just using `.pipe()` directly...