[Solved] Analyze this child process code:const { fork } = require('child_process'); const child = fork('child.js'); child.send('start');... });Why might the parent not receive any messages from the child? | Node.js

Node.js - Worker Threads

Analyze this child process code:

const { fork } = require('child_process');
const child = fork('child.js');
child.send('start');
child.on('message', msg => console.log(msg));

And child.js:

process.on('message', msg => {
  console.log('Child received:', msg);
});

Why might the parent not receive any messages from the child?

AThe parent must call <code>child.disconnect()</code> before receiving messages.

BThe parent should use <code>child.on('data')</code> instead of 'message'.

CThe child.js file path is incorrect, so the child never starts.

DThe child process never sends a message back to the parent.

Step-by-Step Solution

Solution:

Step 1: Check child message handling
The child listens for messages but does not send any back.
Step 2: Parent expects messages
The parent waits for messages, but none are sent, so no output occurs.
Final Answer:
Child never sends messages back to parent. -> Option D
Quick Check:
Child must send messages explicitly [OK]

Quick Trick: Child must send messages to parent explicitly [OK]

Common Mistakes:

Master "Worker Threads" in Node.js

9 interactive learning modes - each teaches the same concept differently

More Node.js Quizzes

Analyze this child process code: