Reading files asynchronously with callbacks in Node.js - Step-by-Step Execution

Concept Flow - Reading files asynchronously with callbacks

Start

↓

Call fs.readFile

↓

Node.js reads file in background

↓

File read complete?

No→Wait

Yes↓

Invoke callback with error or data

↓

Callback processes data or error

↓

End

This flow shows how Node.js starts reading a file, waits in the background, then calls your callback with the result.

Execution Sample

Node.js

const fs = require('fs');
fs.readFile('hello.txt', 'utf8', (err, data) => {
  if (err) {
    console.error('Error:', err);
  } else {
    console.log('File content:', data);
  }
});

Reads 'hello.txt' asynchronously and prints its content or error using a callback.

Execution Table

Step	Action	Evaluation	Result
1	Call fs.readFile with filename, encoding, callback	Starts async file read	File read started, Node.js continues other tasks
2	Node.js reads file in background	File reading in progress	No output yet, waiting
3	File read completes successfully	err is null, data contains file text	Callback invoked with data
4	Callback runs: if err null?	Yes, err is null	Prints 'File content: <file text>'
5	Program continues running	No blocking happened	Ready for next tasks
6	If file read failed	err contains error	Callback prints 'Error: <error message>'

💡 Execution stops after callback runs with either error or data, no blocking occurs.

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 4	Final
err	undefined	undefined	null or Error object	null or Error object	null or Error object
data	undefined	undefined	file content string or undefined	file content string or undefined	file content string or undefined

Key Moments - 3 Insights

Why doesn't the program wait for the file to finish reading before moving on?

Because fs.readFile is asynchronous, it starts reading and immediately returns control. The callback runs later when reading finishes, as shown in execution_table step 1 and 2.

How do we know if reading the file succeeded or failed inside the callback?

The callback receives 'err' and 'data'. If 'err' is null, reading succeeded (step 3). If 'err' has a value, reading failed (step 6).

What happens if we try to use 'data' outside the callback right after calling fs.readFile?

At that moment, 'data' is still undefined because reading is not finished yet. You must use 'data' inside the callback to access the file content.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'err' at step 3 when the file is read successfully?

A undefined

B Error object

C null

D File content string

💡 Hint

Check the 'err' variable value in variable_tracker after step 3.

At which step does the callback function get called?

A Step 3

B Step 5

C Step 1

D Step 6

💡 Hint

Look at execution_table where the callback is invoked with data or error.

If the file does not exist, what will the callback print?

A Nothing, callback is not called

B 'Error: <error message>'

C 'File content: <file text>'

D An empty string

💡 Hint

Refer to execution_table step 6 and key_moments about error handling.

Concept Snapshot

fs.readFile(filename, encoding, callback)
- Starts reading file asynchronously
- Callback(err, data) runs after reading
- err is null if success, else error
- Use data only inside callback
- Program continues without waiting

Full Transcript

This visual execution shows how Node.js reads files asynchronously using fs.readFile. When you call fs.readFile, Node.js starts reading the file in the background and immediately continues running other code. Once the file is fully read or an error occurs, Node.js calls your callback function with two arguments: an error object (or null if no error) and the file data. You check inside the callback if err is null to know if reading succeeded. You must use the file data only inside the callback because outside it is not yet available. This approach avoids blocking your program while waiting for file operations.