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.
| Kind | How this reference treats it |
|---|---|
| React core, stable | Documented as a normal API with Introduced in: React X.X |
| RSC-only | Labeled [RSC] — needs a React Server Components runtime (usually a framework) |
| Framework (Next.js, etc.) | Labeled [framework] — not a React-only feature |
| React Compiler | A separate Babel plugin, not a React runtime hook |
| Experimental / Canary | Labeled [experimental] — never presented as stable |
Timeline & learning path
2 items01Architectural timelineReact 16
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
- This hub (tables + labels)
- Fiber & Reconciliation
- React 16
- Hooks Evolution — skip if you just finished fundamentals L8–L20
- React 17
- Concurrent Rendering
- React 18 APIs
- Suspense & Streaming SSR
- React 19
- Forms & Actions
- Server-oriented React
- 19.1 → 19.2 → 19.3
- Deprecated APIs and Migrations
- Interview & Cheat Sheet
useTransition.02Why each major release existedReact 16
| Release | Why it mattered |
|---|---|
| React 16 | Replace the old stack reconciler with Fiber so rendering can pause, resume, and recover from errors |
| React 16.8 | Make stateful logic reusable without classes (Hooks) |
| React 17 | Make upgrades gradual (two Reacts on one page) and modernize JSX/events without new UI APIs |
| React 18 | Turn Fiber’s concurrency into a public model: Transitions, batching, streaming SSR |
| React 19 | Treat async work (forms, data, optimistic UI, documents) as React’s job, not ad-hoc useEffect |
| React 19.1 | Debug + hydration quality (Owner Stack, useId CSS-safe IDs) |
| React 19.2 | Hide/show UI without losing state (Activity), Effect Events, prerender/resume for frameworks |
| React 19.3 | Stable 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.
createRoot and startTransition are the public switches.”Version → features
2 items03Feature map by versionReact 16
| Feature | Version | Kind | Chapter |
|---|---|---|---|
| Fiber reconciler | 16.0 | Rendering architecture | Fiber |
| Error Boundaries | 16.0 | Major API | React 16 |
| Portals | 16.0 | Major API | React 16 |
Fragments (<>) | 16.2 | API | React 16 |
New Context, createRef, forwardRef, Strict Mode | 16.3 | Major API | React 16 |
| Pointer Events | 16.4 | API | React 16 |
Profiler | 16.5 | DX / performance | React 16 |
memo, lazy, Suspense (code split) | 16.6 | Major API | React 16 |
| Hooks | 16.8 | Major API | Hooks Evolution |
UNSAFE_ lifecycles, act() | 16.9 | Deprecation / DX | Deprecated |
| New JSX transform backport | 16.14 | DX | React 17 |
| New JSX transform, event delegation | 17.0 | DX / rendering | React 17 |
createRoot, automatic batching, concurrent | 18.0 | Rendering architecture | Concurrent |
useTransition, useDeferredValue, useId, useSyncExternalStore, useInsertionEffect | 18.0 | Hooks | React 18 APIs |
Streaming SSR, hydrateRoot | 18.0 | SSR | Suspense & SSR |
Actions, useActionState, useFormStatus, useOptimistic, use() | 19.0 | Major API | React 19 |
Ref as a prop, Context as <Context> | 19.0 | API change | React 19 |
| Document metadata, stylesheets, resource hints | 19.0 | DX / loading | React 19 |
Owner Stack, useId «r» format | 19.1 | DX | 19.1 |
<Activity>, useEffectEvent | 19.2 | Major API | 19.2 |
cacheSignal | 19.2 | RSC-only | 19.2 |
ViewTransition, Fragment refs, browser() | 19.3 | Major API (stable) | 19.3 |
use(), ask: “Does this API exist in react / react-dom, or only if a bundler implements RSC?”useTransition, Action).04Stable vs experimental vs frameworkReact 19
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.
cacheSignal, useOptimistic, and loading.tsx, write core / RSC / framework next to each.Quick maps
1 item05Old API → new APIReact 16
| Old | Status | Replacement |
|---|---|---|
| Stack reconciler | Replaced in 16 | Fiber |
Legacy context (contextTypes) | Deprecated, then removed | createContext (16.3) |
| String refs | Deprecated / removed | createRef (16.3) / ref callback / useRef |
componentWillMount etc. | Renamed UNSAFE_ (16.9), removed in 19 | constructor / useEffect / getDerivedStateFromProps |
ReactDOM.render | Deprecated 18, removed 19 | createRoot (18) |
ReactDOM.hydrate | Deprecated 18, removed 19 | hydrateRoot (18) |
findDOMNode | Deprecated | Refs |
defaultProps on function components | Removed in 19 | Default parameters |
| Classes for state | Still valid | Hooks (16.8) for new code |
Manual pending/error around fetch in submit handlers | Still valid | Actions + useActionState (19) |
| Manual optimistic flags | Still valid | useOptimistic (19) |
forwardRef everywhere | Still valid | ref as a prop (19) |
<Context.Provider> | Still valid | <Context> (19) |
react@19 will not include the old entry point. “Deprecated in 18” means it still ran, with warnings, until 19.index.js. If you still see ReactDOM.render, that app is on the React 17-or-earlier bootstrap path — see Migrations.