Courses
JavaScript Advanced: Code That Holds Up in Production
Check Yourself: Catch Bugs Before You Run the Code
Five scenario questions on JSDoc, type checking and ESLint. 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 add // @ts-check and JSDoc types to a file. What happens when the code runs?
2.
tsc reports "'order' is possibly 'undefined'" on order.total after const order = orders.get(id);. What's the right fix?
3.
Your old project shows 500 ESLint errors on the first run. What's a sound plan?
4.
ESLint reports no-cond-assign on if (status = "paid"). What's the bug?
5.
Which tool catches cartTotal([], "10%") when the function expects a number for the discount?
About
Five scenario questions on JSDoc, type checking and ESLint. If you miss more than one, reread the lesson that covers it.
- Duration
- 5 min
- Last update
- 08/16/2026
Was this helpful?
0
0
Comments (0)
Sign in to commentNo comments yet.