ehmicky
ehmicky
While the `execa.defaultOptions` solution does solve your problem, I think this would create problems for other users. For example, an application might use `execa.defaultOptions` to change the `windowsHide` option on...
Hi @open-source-explorer, I have not tried it locally but would inserting newlines work? ```js const {stdout} = execa(__dirname, args, {input: 'Y\nN\n'}); ```
Yes this sounds good :+1:
`.child` since this is the name used by Node.js `util.promisify(childProcess.exec)`?
@wesleytodd Based on your comment [here](https://github.com/sindresorhus/execa/issues/414#issuecomment-587171732), would you like to take a look at doing a PR for this feature? Please let us know if you need any help!
Hi @Eskibear, What happens if you use `execFile()` instead of `execa()` the following commands show? ```js const { execFile } = require('child_process') const { promisify } = require('util') // Try...
I actually think `execFile()` will not work, i.e. throw an error. This would mean the problem is not specific to Execa but that the command being executed is invalid. `ENOENT`...
Hi @TrevTheDev, Do you mean `stdout` and `stderr`? My answer below assumes that you meant `stdout` instead of `stdin`. I am not sure I understand what you mean. Regardless of...
Hi @lzhaki, Thanks for the feedback! I agree with you, this is confusing. Would you like to add your suggestion as a PR? :)
@wesleytodd thanks your feedback. However this is a separate concern (changing the default value of `extendEnv`) which should be a separate issue.