Courses
JavaScript Advanced: Code That Holds Up in Production
Check Yourself: Data That Doesn't Fit in Memory
Five scenario questions on iterators, generators and streams. If you miss more than one, reread the lesson that covers it.
Course content
Join this Course
Sign in to save your progress.
-
Functions That Remember
-
JavaScript Closures in Real Code
-
this, bind and Arrow Functions: Who Is Calling
-
-
-
How JavaScript Actually Runs
-
The Event Loop: Microtasks, Macrotasks and Why setTimeout(0) Isn't Zero
-
Running Promises in Parallel: all, allSettled, race
-
Cancelling Work With AbortController
-
-
-
Data That Doesn't Fit in Memory
-
Iterators and Generators
-
Streams in Node.js: Reading Big Files a Piece at a Time
-
-
-
Catch Bugs Before You Run the Code
-
JSDoc Types and // @ts-check Without Switching to TypeScript
-
ESLint in a Real Project
-
-
-
Ship It, Then Make It Fast
-
Bundling With Vite and Publishing to npm
-
Finding Slow Code With the Performance Profiler
-
Memory Leaks: Event Listeners and Closures That Never Let Go
-
-
- Final Check: JavaScript Advanced
1.
You loop over a generator object with for...of, then try to loop over the same object again. What happens the second time?
2.
An async generator fetches pages 1, 2, 3 and yields each item. The loop breaks on the second item of page 1. How many pages were fetched?
3.
Why use pipeline from node:stream/promises instead of chaining .pipe()?
4.
You split stream chunks on "\n" yourself and some rows come out broken. Why?
5.
A stream reads a 4 GB CSV line by line, but pushes every row into an array and sums it at the end. Memory runs out. Why?
About
Five scenario questions on iterators, generators and streams. If you miss more than one, reread the lesson that covers it.
- Duration
- 5 min
- Last update
- 08/25/2026
Was this helpful?
0
0
Comments (0)
Sign in to commentNo comments yet.