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
For each of stdin, stdout, and stderr, the stream will be accessible on the child process object if and only if "pipe" was passed as the relevant stdio options. For example, if you did var child = spawn(cmd, args, { stdio: ["pipe", someStream, "pipe"]}, then you would be able to read child.stderr and write child.stdin, but child.stdout would be null.
Currently, we throw an error if you try to access one of the standard streams after spawning it and passing something other than Pipe for that stream. It might be nice to work out how to do this in a safer way than just failing at runtime, if possible.
The text was updated successfully, but these errors were encountered:
As of #46, ChildProcess guarantees that the stdio is always [ pipe, pipe, pipe, ipc ]. However, more control is provided via the Unsafe module if one wants to use something else.
See also joneshf/purescript-node-child-process#4
For each of stdin, stdout, and stderr, the stream will be accessible on the child process object if and only if "pipe" was passed as the relevant stdio options. For example, if you did
var child = spawn(cmd, args, { stdio: ["pipe", someStream, "pipe"]}
, then you would be able to readchild.stderr
and writechild.stdin
, butchild.stdout
would be null.Currently, we throw an error if you try to access one of the standard streams after spawning it and passing something other than
Pipe
for that stream. It might be nice to work out how to do this in a safer way than just failing at runtime, if possible.The text was updated successfully, but these errors were encountered: