ehmicky comments

Results 372 comments of


                                            ehmicky

spawn /path/to/file/code.cmd ENOENT, The system cannot find the path specified.

Hi @bengunnewijkGeonovum, The value of the `cwd` option never needs to be quoted, because it is not interpreted by a shell. Spaces are always allowed in both Unix and Windows....

Fix incorrect execaNode signature in `index.d.ts`

@sindresorhus Is this ok to merge?

feat: setting column on spawned process

Closing as the issue is not related to Node.js.

Allow userland streams to be passed to `stdio` option

We just added 3 methods related to piping: ```js await execa('echo', ['unicorns']).pipeStdout(stream); await execa('echo', ['unicorns']).pipeStderr(stream); await execa('echo', ['unicorns'], {all: true}).pipeAll(stream); ``` For `stdin`, the `input` option can be used with...

Allow userland streams to be passed to `stdio` option

@sindresorhus Should we close this issue?

Allow userland streams to be passed to `stdio` option

See also https://github.com/sindresorhus/execa/issues/617

Support `URL` where paths are supported?

Status update. Done for: - `cwd` option - `localDir` option - `stdin`/`stdout`/`stderr` options Not done for: - `execPath` option - `nodePath` option - `inputFile` option - `file` argument

Support `URL` where paths are supported?

`execPath` done at https://github.com/sindresorhus/npm-run-path/pull/16 and #633 `nodePath` done at #632. `inputFile` done at #630. `file` argument done at https://github.com/sindresorhus/execa/pull/631

Support `URL` where paths are supported?

Only one missing: the `shell` option, done at #635.

Question on stdin and stderr

Closing as stale.