doc: child_process documentation for stdio

[skovhus]

Checklist

• documentation is changed or added
• commit message follows commit guidelines

Affected core subsystem(s)

doc

Description of change

Document that execFileSync, execSync and spawnSync also supports stdio as an Array.

execFileSync, execSync and spawnSync all ends up here, where the options are accepted as string or array. See https://github.com/nodejs/node/blob/master/lib/internal/child_process.js#L758

Fixes: #9636

[Fishrock123]

Your git author information is skovhus <kenneth.skovhus@gmail.com>, are you ok with that or would you like to set more of your name than skovhus?

You can do so via:

git config --global user.name "J. Random User"

Then

git commit --amend --reset-author
git push origin head --force

[skovhus]

@Fishrock123 I've updated with full name... Thanks 👍

[sam-github]

You commit message should describe the changes, it doesn't now.

I suggest something like:

doc: child_process .stdio accepts an Array type

[skovhus]

@sam-github thanks, I've updated the commit message.

[sam-github]

@skovhus I'm sorry, I typed too quickly, and you accepted my suggestion too quickly.... it's the String type you added to the docs, Array was pre-existing.

[skovhus]

@sam-github my bad. Should be all right now.

[silverwind]

Thanks! Landed in 6df167c.

[skovhus]

Thanks. When are the docs released? Would that be with the next release of node or do you update existing documentation?

[skovhus]

@silverwind

[addaleax]

do you update existing documentation?

The docs under https://nodejs.org/docs/ always refer to released versions and are fixed for a specific released version.

Would that be with the next release of node

Generally, yes – but that’s only scheduled 3 days from now. It would be awesome if you could check for which release lines (v4.x, v6.x, v7.x) this updated documentation applies so that we know to which of these it should be applied, too.

[skovhus]

@addaleax thanks for clarifying.

It would be awesome if you could check for which release lines (v4.x, v6.x, v7.x) this updated documentation applies so that we know to which of these it should be applied, too.

I just checked that this documentation update applies for v4-7. So should I do a pull request where this is cherry picked into the v4.x and v5.x branch?

[addaleax]

@skovhus Since this doesn’t apply cleanly to v4.x, I think that would be appreciated; you’ll want to target the v4.x-staging branch for that.

v5.x is no longer maintained and this cherry-picks cleanly onto the v6.x and v7.x staging branches, so there’s nothing to do there. :)

[skovhus]

@addaleax ok, I've made a pull for updating v4.x-staging. : )

[addaleax]

@skovhus thanks! :)