TypeError: Cannot read property 'on' of null

[BumpyBill]

• Version: v6.14.4
• Platform: Linux S204394 4.4.0-18362-Microsoft --abort-on-uncaught-exception prevents domains from working at all (the process crashes) #836-Microsoft Mon May 05 16:04:00 PST 2020 x86_64 x86_64 x86_64 GNU/Linux (Windows 64)
• Subsystem: WSL (Ubuntu 20.04.1)

What steps will reproduce the bug?

const { spawn } = require("child_process");

const deploy = spawn("sh", ["-c", `node server && ls`], {
  stdio: ["inherit", "inherit", "inherit"],
});

console.log(deploy.pid); // I use this to get the PID so i can use the kill command

deploy.stdout.on("data", (data) => {
  console.log(data.toString());
});

deploy.stderr.on("data", (data) => {
  console.log(data.toString());
});

deploy.on("exit", (code) => {
  console.log("exit");
});

How often does it reproduce? Is there a required condition?

From what I can tell, it seems to happen every time

What is the expected behavior?

To run the code as it would

What do you see instead?

deploy.stdout.on("data", (data) => {
             ^

TypeError: Cannot read property 'on' of null
    at Object.<anonymous> (/mnt/c/Users/624234/Desktop/Testing/aaaa/index.js:9:14)
    at Module._compile (module.js:577:32)
    at Object.Module._extensions..js (module.js:586:10)
    at Module.load (module.js:494:32)
    at tryModuleLoad (module.js:453:12)
    at Function.Module._load (module.js:445:3)
    at Module.runMain (module.js:611:10)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:160:9)
    at bootstrap_node.js:507:3

[BumpyBill]

After doing a bit of debugging, thedeploy variable is equal to:

ChildProcess {
  domain: null,
  _events: {},
  _eventsCount: 0,
  _maxListeners: undefined,
  _closesNeeded: 1,
  _closesGot: 0,
  connected: false,
  signalCode: null,
  exitCode: null,
  killed: false,
  spawnfile: 'sh',
  _handle: Process { owner: [Circular], onexit: [Function], pid: 3439 },
  spawnargs: [ 'sh', '-c', 'node server && ls' ],
  pid: 3439,
  stdin: null,
  stdout: null,
  stderr: null,
  stdio: [ null, null, null ]
}

[JamesGaier]

I was reading the documentation on child processes and I noticed that if you pass anything other than 'pipe' to stdio[1], stdout is set to null.

[targos]

This is not a bug and documented, so I'll close the issue.