From d4bcb3689dddc5daea365cd3925e030dc9549ec9 Mon Sep 17 00:00:00 2001
From: James M Snell <jasnell@gmail.com>
Date: Mon, 4 Jan 2021 11:26:51 -0800
Subject: [PATCH] doc: clarify subprocess.stdout/in/err/io properties

The various `subprocess.stdwhatever` properties can be null or
undefined in certain conditions.

Fixes: https://github.com/nodejs/node/issues/33458
Signed-off-by: James M Snell <jasnell@gmail.com>

PR-URL: https://github.com/nodejs/node/pull/36784
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
---
 doc/api/child_process.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/doc/api/child_process.md b/doc/api/child_process.md
index 40172705f517c9..6b092a83018d3c 100644
--- a/doc/api/child_process.md
+++ b/doc/api/child_process.md
@@ -1508,6 +1508,9 @@ then this will be `null`.
 `subprocess.stderr` is an alias for `subprocess.stdio[2]`. Both properties will
 refer to the same value.
 
+The `subprocess.stderr` property can be `null` if the child process could
+not be successfully spawned.
+
 ### `subprocess.stdin`
 <!-- YAML
 added: v0.1.90
@@ -1526,6 +1529,9 @@ then this will be `null`.
 `subprocess.stdin` is an alias for `subprocess.stdio[0]`. Both properties will
 refer to the same value.
 
+The `subprocess.stdin` property can be `undefined` if the child process could
+not be successfully spawned.
+
 ### `subprocess.stdio`
 <!-- YAML
 added: v0.7.10
@@ -1566,6 +1572,9 @@ assert.strictEqual(subprocess.stdio[2], null);
 assert.strictEqual(subprocess.stdio[2], subprocess.stderr);
 ```
 
+The `subprocess.stdio` property can be `undefined` if the child process could
+not be successfully spawned.
+
 ### `subprocess.stdout`
 <!-- YAML
 added: v0.1.90
@@ -1591,6 +1600,9 @@ subprocess.stdout.on('data', (data) => {
 });
 ```
 
+The `subprocess.stdout` property can be `null` if the child process could
+not be successfully spawned.
+
 ### `subprocess.unref()`
 <!-- YAML
 added: v0.7.10