You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently return the child process' stdout and stderr, as a property to the result and error objects.
We could do the same for the other file descriptors (3, 4, etc.), using childProcess.stdio. This would useful to any users writing to custom file descriptors.
It would behave just like stdout and stderr when it comes to buffering and encoding. It would in fact mostly use the same existing underlying logic, so the implementation would be fairly lightweight.
Just like stdout and stderr, it would be undefined when using inherit, ignore, ipc, etc. since those do leave childProcess.stdio[*] as null.
We currently return the child process'
stdout
andstderr
, as a property to the result and error objects.We could do the same for the other file descriptors (3, 4, etc.), using
childProcess.stdio
. This would useful to any users writing to custom file descriptors.It would behave just like
stdout
andstderr
when it comes to buffering and encoding. It would in fact mostly use the same existing underlying logic, so the implementation would be fairly lightweight.Just like
stdout
andstderr
, it would beundefined
when usinginherit
,ignore
,ipc
, etc. since those do leavechildProcess.stdio[*]
asnull
.childProcess.spawnSync()
actually does exactly this.What do you think @sindresorhus?
The text was updated successfully, but these errors were encountered: