Roadmaps / JavaScript
Programming Languages · 16 study weeks · 4 phases
JavaScript Roadmap Beta
JavaScript runs in browsers, on servers and at the edge, and it fails in ways that only show up under load or in someone else's browser. These 16 study weeks teach the language, its two main runtimes (the browser and Node.js) and how to ship it safely. You build one service, a link preview service, in plain JavaScript with no framework, and every phase adds a checkpoint to it. At 8 hours a week the core path is 128 hours and takes 16 weeks. At 12 hours a week it takes about 11 weeks, and at 16 hours a week about 8 weeks. At the end you can explain, with measurements, why a Node service stalls, leaks or gets attacked, and you can fix it. This roadmap uses plain JavaScript on purpose, so the language is the thing you learn. Types have their own roadmap, TypeScript.
This roadmap is in beta and keeps improving over time. If you spot an error, please email your suggestions and corrections to [email protected].
Read first
Phase 1 · Study weeks 1-4
The language, the event loop and bounded concurrency
This phase makes the first checkpoint possible: a fetch core that never runs away, stops when told and shows when it blocks.
- 5 repos
- Milestone checkpoint
- Study week 1Values, coercion and equality8 h
- Study week 2Iterators, generators and symbols8 h
- Study week 3The Node event loop phases and the browser's task and render cycle8 h
- Study week 4Concurrency limits and per-key queues8 h
Phase 2 · Study weeks 5-8
Modules, streams, workers and correct data
This phase makes the second checkpoint possible: a service that reads untrusted bodies safely, keeps CPU work off the event loop and ships as a package other code can import.
- 5 repos
- Milestone checkpoint
- Study week 5ES modules and CommonJS interop8 h
- Study week 6Web Streams and Node streams8 h
- Study week 7Worker threads and message passing8 h
- Study week 8Floating point, BigInt and money8 h
Phase 3 · Study weeks 9-12
The browser, the engine and memory
This phase makes the third checkpoint possible: a page that responds quickly with thousands of items, and a server whose memory you can explain.
- 5 repos
- Milestone checkpoint
- Study week 9The browser rendering pipeline8 h
- Study week 10Hidden classes and inline caches8 h
- Study week 11Garbage collection: generations and pauses8 h
- Study week 12Profiling with DevTools and node --cpu-prof8 h
Phase 4 · Study weeks 13-16
Security, tests and shipping
This phase makes the last checkpoint possible: a service you can defend, test, observe and upgrade.
- 5 repos
- Milestone checkpoint
- Study week 13SSRF and DNS rebinding8 h
- Study week 14Lockfiles and npm ci8 h
- Study week 15node:test8 h
- Study week 16Structured logs and tracing8 h