Handling child process errors in Node.js - Step-by-Step Execution

Concept Flow - Handling child process errors

Start child process

↓

Child process runs

↓

Error occurs?

No→Process ends successfully

Yes↓

Emit 'error' event

↓

Error handler runs

↓

Log or handle error

↓

Process ends with error

This flow shows how a Node.js child process starts, runs, and if an error happens, it emits an error event that is caught and handled.

Execution Sample

Node.js

import { spawn } from 'child_process';

const child = spawn('invalidCommand');

child.on('error', (err) => {
  console.error('Error:', err.message);
});

This code tries to run a non-existing command and listens for errors emitted by the child process.

Execution Table

Step	Action	Evaluation	Result
1	Spawn child process with 'invalidCommand'	Command not found	Child process emits 'error' event
2	Error event listener triggers	Receives error object	Logs error message 'Error: spawn invalidCommand ENOENT'
3	Process ends	No further events	Child process terminates with error

💡 Child process fails to start due to invalid command, triggering error event and ending process

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
child	undefined	ChildProcess object created	Error event listener attached	Child process terminated with error

Key Moments - 2 Insights

Why does the 'error' event get emitted instead of 'exit' when the command is invalid?

Because the child process fails to start at all, Node.js emits an 'error' event immediately (see execution_table step 1), not an 'exit' event which happens after a process runs.

What happens if we don't attach an 'error' event listener?

The program will crash with an uncaught error when the child process fails to start, as shown by the error event in execution_table step 2 requiring a handler.

Visual Quiz - 3 Questions

Look at the execution table, what happens at step 2?

A The error event listener runs and logs the error message

B The child process starts successfully

C The process exits without error

D The command runs and outputs data

💡 Hint

Check the 'Action' and 'Result' columns in execution_table row 2

At which step does the child process emit the 'error' event?

A Step 3

B Step 1

C Step 2

D No error event is emitted

💡 Hint

Look at the 'Evaluation' column in execution_table row 1

If the command was valid, how would the execution table change?

A The process would emit an 'error' event anyway

B The error event listener would still run

C There would be no 'error' event emitted in step 1

D The child variable would be undefined

💡 Hint

Refer to the 'Result' column in execution_table row 1 about error emission

Concept Snapshot

Handling child process errors in Node.js:
- Use spawn() to start a child process.
- Attach an 'error' event listener to catch startup errors.
- If the command is invalid, 'error' event fires immediately.
- Without error handler, program crashes on startup failure.
- Always handle 'error' to keep your app stable.

Full Transcript

This lesson shows how Node.js handles errors when starting child processes. When you use spawn() to run a command, if the command does not exist, the child process cannot start. Node.js then emits an 'error' event. You must listen for this event to catch the error and prevent your program from crashing. The example code runs an invalid command and logs the error message when the 'error' event fires. The execution table traces these steps: spawning the process, error event emission, error handling, and process termination. Key points include understanding why 'error' fires instead of 'exit' and the importance of attaching an error listener. The quiz tests your understanding of these steps and what changes if the command is valid.