Error-first callback convention in Node.js - Step-by-Step Execution

Concept Flow - Error-first callback convention

Function called

↓

Operation starts

↓

Operation finishes

↓

Check for error

↓

Call callback

This flow shows how a function performs an operation, then calls a callback with an error first if any, or with the result if no error.

Execution Sample

Node.js

function readFile(callback) {
  let error = null;
  let data = 'file content';
  callback(error, data);
}

readFile((err, content) => {
  if (err) console.error(err);
  else console.log(content);
});

This code simulates reading a file and calls a callback with error first, then data.

Execution Table

Step	Action	Error Value	Data Value	Callback Called With
1	Function readFile called	undefined	undefined	No
2	Operation starts (simulate reading)	null	undefined	No
3	Operation finishes	null	'file content'	No
4	Callback called with error and data	null	'file content'	callback(null, 'file content')
5	Callback executes: err check	null	'file content'	No error branch taken, logs 'file content'

💡 Callback called once with error=null and data='file content', execution ends.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
error	undefined	null	null	null	null
data	undefined	undefined	'file content'	'file content'	'file content'

Key Moments - 2 Insights

Why is the error argument always first in the callback?

Because the convention is to check for errors first before processing data, as shown in step 4 and 5 of the execution_table.

What happens if there is an error?

The callback is called with the error as the first argument and usually no data, so the error branch is taken immediately, as the flow diagram shows.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'error' when the callback is called?

A 'file content'

B null

C undefined

D An Error object

💡 Hint

Check the 'Error Value' column at step 4 in the execution_table.

At which step does the callback get called with the data?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Callback Called With' column in the execution_table.

If an error occurred, how would the callback call change in the execution_table?

A callback(error, null)

B callback(data, error)

C callback(null, data)

D callback(data)

💡 Hint

Refer to the concept_flow where error is passed first if present.

Concept Snapshot

Error-first callback convention:
- Callback signature: callback(error, result)
- Always check error first
- If error exists, handle it immediately
- If no error, process the result
- Keeps async code clear and consistent

Full Transcript

In Node.js, many functions use the error-first callback pattern. This means the callback function receives an error as its first argument and the result as the second. When the function finishes its operation, it calls the callback. If there was an error, it passes that error first and usually no result. If no error occurred, it passes null for the error and the actual result as the second argument. This pattern helps developers quickly check for errors before using the data. The example code simulates reading a file and calls the callback with null error and file content. The execution table shows each step, including when the callback is called and how variables change. Understanding this flow helps avoid confusion when working with asynchronous Node.js code.