0
Challenge · 93React Internals
Scheduler
Internalsused in ~15% of apps
JavaScript runs on one thread. If React rendered a huge update in one blocking pass, the page would freeze — no typing, no scrolling — until it finished. The Scheduler is what lets React stay responsive anyway.
Core idea. The Scheduler assigns every update a priority and slices rendering into small chunks, so React can do urgent work first, pause low-priority work, and hand the thread back to the browser instead of blocking it.
poke it, drag it,
try to break it
try to break it
no slides here.
you drive.
you drive.
Playground, this isn't a screenshot
URGENT lane · typingkeystrokes handled: 0
LOW-PRIORITY lane · big list render0/20 units committed
React renders this list in slices, yielding to the browser every ~5ms — so an urgent keystroke can cut in, then the list resumes.
Concurrent: the scheduler does the urgent work first and interrupts the low-priority list, so typing stays instant.
↑ play a little first, then dig in