Reading data with Readable streams in Node.js - Step-by-Step Execution

Concept Flow - Reading data with Readable streams

Create Readable Stream

↓

Attach 'data' event listener

↓

Stream emits chunk

→Receive chunk in listener

↓

Process chunk (e.g., print or store)

↓

Stream emits 'end'

→Stop reading

↓

Close stream

The flow shows creating a readable stream, listening for data chunks, processing each chunk, and stopping when the stream ends.

Execution Sample

Node.js

const fs = require('fs');
const stream = fs.createReadStream('file.txt');
stream.on('data', chunk => {
  console.log(chunk.toString());
});
stream.on('end', () => {
  console.log('Finished reading');
});

This code reads a file in chunks and prints each chunk until the file is fully read.

Execution Table

Step	Event Emitted	Chunk Content	Action Taken	Output
1	data	Hello	Print chunk	Hello
2	data	World!	Print chunk	World!
3	end	null	Print finished message	Finished reading
4	none	null	No more data, stop reading	Stream closed

💡 Stream emits 'end' event, no more data to read

Variable Tracker

Variable	Start	After 1	After 2	After 3	Final
chunk	undefined	"Hello "	"World!"	null	null
stream.readableEnded	false	false	false	true	true

Key Moments - 3 Insights

Why do we get multiple 'data' events instead of one big chunk?

Because streams read data in small pieces (chunks) to avoid loading everything into memory at once, as shown in execution_table rows 1 and 2.

What does the 'end' event mean in the stream?

It means the stream has no more data to provide, so reading stops, as shown in execution_table row 3.

Why do we convert chunk to string before printing?

Chunks are Buffer objects by default; converting to string makes the data readable, as seen in the code sample.

Visual Quiz - 3 Questions

Look at the execution table, what is the chunk content at step 2?

A "World!"

B "Hello "

C null

D "Finished reading"

💡 Hint

Check the 'Chunk Content' column at step 2 in the execution_table.

At which step does the stream indicate it has finished reading?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look for the 'end' event in the 'Event Emitted' column in execution_table.

If the file was empty, which event would be emitted first?

A 'data'

B 'end'

C 'error'

D 'close'

💡 Hint

Refer to the concept_flow where 'end' means no data to read.

Concept Snapshot

Readable streams let you read data piece by piece.
Use 'data' event to get chunks as they arrive.
Use 'end' event to know when reading is done.
Chunks are Buffers; convert to string to read.
This helps handle large files without loading all at once.

Full Transcript

In Node.js, reading data with readable streams means you get data in small parts called chunks. You create a stream from a source like a file. Then you listen for 'data' events to receive chunks. Each chunk is a Buffer, so you convert it to string to see the content. When the stream finishes, it emits an 'end' event, telling you no more data is coming. This way, you can process large files efficiently without loading everything into memory at once.