~/alexsh.blog

$ cd writing/react-internals && cat README

React Internals

How React works under the hood: Fiber, the render and commit phases, hooks, concurrency and the compiler, traced through the React 18/19 source.

→ start at 01-the-pipeline13 parts · ~13 min · February 9, 2026

$ ls -l

  1. 01The PipelineWhen you write <App />, a chain of transformations runs before pixels reach the screen.1 min
  2. 02Fiber ArchitectureFiber is React's internal reconciliation engine, introduced in React 16 as a complete rewrite.1 min
  3. 03Render PhaseThe render phase is where React figures out what changed.1 min
  4. 04Commit PhaseThe commit phase is synchronous — once started, it runs to completion.1 min
  5. 05How Hooks WorkHooks are a linked list stored on fiber.memoizedState.1 min
  6. 06Concurrent FeaturesReact 18+ can prepare several UI versions at once and interrupt low-priority work for urgent updates.1 min
  7. 07Context InternalsHow a Provider change walks the subtree and reaches consumers, even through memoized ancestors.1 min
  8. 08Event SystemReact doesn't attach listeners to individual DOM nodes.1 min
  9. 09Server ComponentsServer Components run on the server and stream the Flight protocol to the client, not HTML.1 min
  10. 10React CompilerAn ahead-of-time compiler that memoizes components and hooks at build time.1 min
  11. 11MisconceptionsCommon beliefs about React that the source code contradicts.1 min
  12. 12Source MapThe key files in the React monorepo and what each one does.1 min
  13. 13ResourcesThe reading, talks and deep dives worth your time after this series.1 min