Timeline hub

React Evolution

Timeline from React 16 through 19.3: why each era existed, what to learn next, and how to tell stable APIs from RSC, framework, and experimental features. · 5 lessons · click a card to expand

Part of the React 16 → 19.3 evolution reference. Expand a card, then use chapter links in the sidebar.

Read this hub first, then follow the chapter order in the sidebar. Every important API in later chapters names the version that introduced it, the problem it solved, and when not to use it.

KindHow this reference treats it
React core, stableDocumented as a normal API with Introduced in: React X.X
RSC-onlyLabeled [RSC] — needs a React Server Components runtime (usually a framework)
Framework (Next.js, etc.)Labeled [framework] — not a React-only feature
React CompilerA separate Babel plugin, not a React runtime hook
Experimental / CanaryLabeled [experimental] — never presented as stable

Timeline & learning path

2 items
01Architectural timelineReact 16
Introduced in: React 16. React’s public story from 16 to 19.3 is one idea: make rendering interruptible, then make async UI (forms, server, optimistic updates) a first-class model. Each major release solved a different bottleneck.
React did not add random APIs. Each era unblocked the next.
text
React 16  Fiber, Error Boundaries, Fragments, Portals
    |
    v
16.3      New Context, createRef, forwardRef, Strict Mode
    |
    v
16.6      memo, lazy, Suspense (code splitting)
    |
    v
16.8      Hooks
    |
    v
React 17  JSX transform, event delegation, gradual upgrades
    |
    v
React 18  Concurrent rendering, createRoot, Transitions, automatic batching
    |
    v
React 19  Actions, use(), optimistic UI, ref-as-prop, document metadata
    |
    v
19.1      Owner Stack, useId format, hydration/scheduling
    |
    v
19.2      Activity, useEffectEvent, Performance Tracks, partial prerender
    |
    v
19.3      ViewTransition (stable), Fragment refs (stable), browser()

Why this timeline matters

If you skip Fiber, concurrent APIs feel like magic. If you skip React 17, you will not understand why createRoot and the new JSX runtime exist. If you skip React 18, React 19 Actions look like “forms got a new hook” instead of “async UI is now scheduled work.”

Recommended learning flow

  1. This hub (tables + labels)
  2. Fiber & Reconciliation
  3. React 16
  4. Hooks Evolution — skip if you just finished fundamentals L8–L20
  5. React 17
  6. Concurrent Rendering
  7. React 18 APIs
  8. Suspense & Streaming SSR
  9. React 19
  10. Forms & Actions
  11. Server-oriented React
  12. 19.1 → 19.2 → 19.3
  13. Deprecated APIs and Migrations
  14. Interview & Cheat Sheet
Tip: Do not memorize patch numbers. Memorize the *job* of each era: 16 = new engine, 17 = install safely, 18 = schedule work, 19 = async UI.
Try it: After this page, open Fiber and explain render vs commit out loud before you touch useTransition.
02Why each major release existedReact 16
Introduced in: React 16 (the pattern continues through 19). A “why this release mattered” answer is architectural, not a bullet list of APIs.
Release notes list features. This table lists the problem the team was actually solving.
ReleaseWhy it mattered
React 16Replace the old stack reconciler with Fiber so rendering can pause, resume, and recover from errors
React 16.8Make stateful logic reusable without classes (Hooks)
React 17Make upgrades gradual (two Reacts on one page) and modernize JSX/events without new UI APIs
React 18Turn Fiber’s concurrency into a public model: Transitions, batching, streaming SSR
React 19Treat async work (forms, data, optimistic UI, documents) as React’s job, not ad-hoc useEffect
React 19.1Debug + hydration quality (Owner Stack, useId CSS-safe IDs)
React 19.2Hide/show UI without losing state (Activity), Effect Events, prerender/resume for frameworks
React 19.3Stable View Transitions and Fragment refs; client-only browser(); Trusted Types

What did *not* change

React’s public contract is still: UI = f(state). Fiber, concurrent rendering, and Actions change *how* React computes and commits that function, not the mental model of components and props.

Tip: In interviews, lead with the era’s job, then name two APIs. “React 18 made rendering interruptible; createRoot and startTransition are the public switches.”
Try it: Write one sentence per major version (16, 17, 18, 19) without naming more than two APIs.

Version → features

2 items
03Feature map by versionReact 16
Introduced in: the version in each row. Use this table to jump to the right chapter. Tiny patches are omitted unless they changed how you write React.
This is the index. Depth lives on the linked chapters.
FeatureVersionKindChapter
Fiber reconciler16.0Rendering architectureFiber
Error Boundaries16.0Major APIReact 16
Portals16.0Major APIReact 16
Fragments (<>)16.2APIReact 16
New Context, createRef, forwardRef, Strict Mode16.3Major APIReact 16
Pointer Events16.4APIReact 16
Profiler16.5DX / performanceReact 16
memo, lazy, Suspense (code split)16.6Major APIReact 16
Hooks16.8Major APIHooks Evolution
UNSAFE_ lifecycles, act()16.9Deprecation / DXDeprecated
New JSX transform backport16.14DXReact 17
New JSX transform, event delegation17.0DX / renderingReact 17
createRoot, automatic batching, concurrent18.0Rendering architectureConcurrent
useTransition, useDeferredValue, useId, useSyncExternalStore, useInsertionEffect18.0HooksReact 18 APIs
Streaming SSR, hydrateRoot18.0SSRSuspense & SSR
Actions, useActionState, useFormStatus, useOptimistic, use()19.0Major APIReact 19
Ref as a prop, Context as <Context>19.0API changeReact 19
Document metadata, stylesheets, resource hints19.0DX / loadingReact 19
Owner Stack, useId «r» format19.1DX19.1
<Activity>, useEffectEvent19.2Major API19.2
cacheSignal19.2RSC-only19.2
ViewTransition, Fragment refs, browser()19.3Major API (stable)19.3
Tip: If a blog post mixes Next.js App Router with use(), ask: “Does this API exist in react / react-dom, or only if a bundler implements RSC?”
Try it: Pick one production bug you have seen and name the *version* that introduced the right tool (batching, Error Boundary, useTransition, Action).
04Stable vs experimental vs frameworkReact 19
Introduced in: React 19 era (the distinction matters most here). Mixing React core, Canary, RSC, Next.js, and the Compiler is the #1 way this reference would lie to you.
React ships on multiple tracks.

React core (react, react-dom)

What you import in a Vite SPA: hooks, createRoot, <Suspense>, <Activity>, useEffectEvent, ViewTransition (19.3).

React Server Components

RSC is a React architecture implemented by a bundler/framework. cache(), cacheSignal, and 'use server' as a file convention are not things a client-only CRA/Vite app can use by importing react.

Next.js (and other frameworks)

App Router, loading.tsx, file-system routing, cookies(), redirect(), and many “Server Action” ergonomics are framework. React 19 documents the underlying Actions / Server Functions model; Next.js is the common implementation.

React Compiler

babel-plugin-react-compiler (often via react-compiler). It auto-memoizes. It is not a new hook and not tied to a single React minor the way useTransition is.

Canary / experimental

APIs can land in react@canary or react@experimental before a stable minor. This reference labels them [experimental] and will not call them production-default.

Tip: When reading a tweet about a “new React API,” check react.dev/blog and the changelog before you put it in a design doc.
Try it: For cacheSignal, useOptimistic, and loading.tsx, write core / RSC / framework next to each.

Quick maps

1 item
05Old API → new APIReact 16
Introduced in: various (see Replacement column). Evolution is easier if you remember pairs, not isolated names.
Use this as a flashcard table. Details and caveats are in Deprecated APIs.
OldStatusReplacement
Stack reconcilerReplaced in 16Fiber
Legacy context (contextTypes)Deprecated, then removedcreateContext (16.3)
String refsDeprecated / removedcreateRef (16.3) / ref callback / useRef
componentWillMount etc.Renamed UNSAFE_ (16.9), removed in 19constructor / useEffect / getDerivedStateFromProps
ReactDOM.renderDeprecated 18, removed 19createRoot (18)
ReactDOM.hydrateDeprecated 18, removed 19hydrateRoot (18)
findDOMNodeDeprecatedRefs
defaultProps on function componentsRemoved in 19Default parameters
Classes for stateStill validHooks (16.8) for new code
Manual pending/error around fetch in submit handlersStill validActions + useActionState (19)
Manual optimistic flagsStill validuseOptimistic (19)
forwardRef everywhereStill validref as a prop (19)
<Context.Provider>Still valid<Context> (19)
Tip: “Removed in 19” means react@19 will not include the old entry point. “Deprecated in 18” means it still ran, with warnings, until 19.
Try it: Open a legacy app’s index.js. If you still see ReactDOM.render, that app is on the React 17-or-earlier bootstrap path — see Migrations.