nano-spawn's design goal is to have a small package size. As such, it is intentionally missing some features. Execa provides with those missing features, if a user needs them. Alternatively, users have access to the underlying subprocess, so they can achieve most of what they want.
Node.js or web streams (as opposed to iterables). However, users will be able to pass those to the native stdin/stdout/stderr option, e.g. {stdout: createWriteStream('./output.txt')}.
Background issue at https://github.com/sindresorhus/execa/issues/1147
nano-spawn's design goal is to have a small package size. As such, it is intentionally missing some features. Execa provides with those missing features, if a user needs them. Alternatively, users have access to the underlying
subprocess
, so they can achieve most of what they want.This issue lists those missing features:
stdin
/stdout
/stderr
option, e.g.{stdout: createWriteStream('./output.txt')}
.stdio
. However, they cannot be iterated nor retrieved.result.failed
/error.failed
boolean.stderr
, bothstderr
+stdout
, or other file descriptorsstdin
@sindresorhus Please let me know if this list is incorrect.