effect-command-executor

Use ChildProcess.make to build the command, then call spawner.string or spawner.lines from the ChildProcessSpawner service to execute it and capture output. These helpers manage Scope internally, so no explicit Effect.scoped is needed.

Use spawner.string for raw stdout as a single string and spawner.lines for an array of output lines. For per-chunk processing, use spawner.spawn and consume handle.all as a Stream with Stream.decodeText and Stream.splitLines.

Yes, ChildProcess.pipeTo connects one command's output to another's stdin, equivalent to a shell pipeline. Options let you pipe stderr or combined stdout+stderr instead of the default stdout.

spawner.spawn returns a handle that requires a Scope for cleanup. Wrap the program in Effect.scoped so the process is terminated when the scope closes, or use spawner.string/lines which handle scoping internally.

Child process operations fail with PlatformError, which you can catch with Effect.catchTag or map into typed domain errors using Effect.mapError with a Schema.TaggedError class. Avoid exposing PlatformError in your service API.

Use spawn when you need the process handle for interactive control: writing to stdin, streaming output while the process runs, checking isRunning, or killing with a custom signal. For simple output capture, string and lines are sufficient.