ehmicky

The discussion in core Node.js was very insightful. The first thing is: at the syscall level (using Linux as an example), [`exec`](https://www.man7.org/linux/man-pages/man3/exec.3.html) spawns the program with only its arguments and...

Although this issue has been open for almost 7 years now, this would still be a very valuable feature. Some of the points anyone implementing this should consider: - Cross-platform...

Yes, I think this is a nice idea in general. ## Escaping Escaping is one of the most common sources of confusion with process execution. We have closed many non-issues...

Thank you so much @aaronccasanova for the draft PR! :heart: I really like the minimalist approach of this. > Is whitespace escaping enough though? Just want to make sure we...

Sorry for the confusion! Let me clarify what I mean. `execaCommand()` itselfs de-sugars to `execa()`, once whitespace parsing/escaping has been performed. `execa()` itself just sends the arguments as is to...

Thanks for providing the links to `zx`'s approach, that's very interesting. :book: One important issue with this approach is that this is Bash-specific. This will break for users of shells...

Execa is not currently shell-specific. Requiring a specific shell to use specific features might be a problem to many users, including myself (I am not using `zsh`). Except if those...

This is current in progress at #510 thanks to @aaronccasanova's great work! :clap:

Released in [`v7.1.0`](https://github.com/sindresorhus/execa/releases/tag/v7.1.0).

I am wondering whether the [new pipe methods](https://github.com/sindresorhus/execa#inputoutput) might already be fixing the underlying problem of this issue? ```js // stdout -> stdin await execa(...).pipeStdout(execa(...)) // stdout -> stream await...