spawn() vs. spawnChild().output()

[mfulton26]

From what I can tell Deno.spawn() and Deno.spawnChild().output() do the same thing. Should Deno.spawn() be dropped and Deno.spawnChild() be renamed to Deno.spawn()? Deno standard library can define convenience APIs where desired but it seems odd to me to have 2 simple ways to do the same thing. Am I missing something?

spawn.ts
const { code, stdout, stderr } = await Deno.spawn(Deno.execPath(), { args: [ "eval", "console.log('hello'); console.error('world')", ], }); console.assert(code === 0); console.assert("hello\n" === new TextDecoder().decode(stdout)); console.assert("world\n" === new TextDecoder().decode(stderr));

spawnChild.ts
const child = Deno.spawnChild(Deno.execPath(), { args: [ "eval", "console.log('hello'); console.error('world')", ], }); const { code, stdout, stderr } = await child.output(); console.assert(code === 0); console.assert("hello\n" === new TextDecoder().decode(stdout)); console.assert("world\n" === new TextDecoder().decode(stderr));

diff -u spawn.ts spawnChild.ts

--- spawn.ts 2022-09-08 08:45:55.000000000 -0500 +++ spawnChild.ts 2022-09-08 08:46:05.000000000 -0500 @@ -1,9 +1,10 @@ -const { code, stdout, stderr } = await Deno.spawn(Deno.execPath(), { +const child = Deno.spawnChild(Deno.execPath(), { args: [ "eval", "console.log('hello'); console.error('world')", ], }); +const { code, stdout, stderr } = await child.output(); console.assert(code === 0); console.assert("hello\n" === new TextDecoder().decode(stdout)); console.assert("world\n" === new TextDecoder().decode(stderr));