FlashcardsRecall, then flip

Print · React 19

Back to study

16 cards · 2 sheets · 4 pages.

Print double-sided, flipping on the long edge, at 100% scale with no margins added by the browser. Answer columns are already mirrored, so each answer lands on the back of its own question. Cut along the dashed lines.

Preview

React 19 flashcards — questions (cards 1-8)Print double-sided, flip on long edge, cut along dashed lines
CARD 1 · QUESTION

What is the latest React version, and is 'React 20' real?

CARD 2 · QUESTION

What are Actions in React 19?

CARD 3 · QUESTION

What does useActionState do?

CARD 4 · QUESTION

What does useFormStatus do?

CARD 5 · QUESTION

What does useOptimistic do?

CARD 6 · QUESTION

What is the use() API?

CARD 7 · QUESTION

What are React Server Components (RSC)?

CARD 8 · QUESTION

'use client' vs 'use server' — what does each mark?

React 19 flashcards — answers (cards 1-8)Columns mirrored so answers align with question backs
CARD 2 · ANSWER

Async functions passed to a transition or form. React automatically manages the pending state, error handling, optimistic updates, and form resets you used to hand-write.

CARD 1 · ANSWER

React 19.2 (19.0 shipped Dec 2024; 19.2 landed Oct 2025). No React 20 exists. React is now stewarded by the independent React Foundation under the Linux Foundation.

CARD 4 · ANSWER

Lets a child component read the status (pending, data) of its nearest parent <form> — like context for forms. Classic use: a submit button that disables itself.

CARD 3 · ANSWER

Wraps an action and returns [state, formAction, isPending] — replacing hand-rolled loading/error/result state for submissions. Pass formAction straight to <form action={...}>.

CARD 6 · ANSWER

Reads a promise or context during render, suspending until the promise resolves. Unlike hooks, use() can be called conditionally and inside loops.

CARD 5 · ANSWER

Shows a temporary 'optimistic' value while an async action is in flight, then automatically reverts to the real state when the action completes or fails.

CARD 8 · ANSWER

'use client': the boundary where components ship to the browser. 'use server': marks Server Functions callable from the client — NOT server components (those are the default, no directive).

CARD 7 · ANSWER

Components that run only on the server and send serialized UI — not JavaScript — to the client. Zero bundle cost. 'use client' marks where the client-side world begins.

React 19 flashcards — questions (cards 9-16)Print double-sided, flip on long edge, cut along dashed lines
CARD 9 · QUESTION

What replaced forwardRef?

CARD 10 · QUESTION

How does React 19 handle <title> and <meta> tags?

CARD 11 · QUESTION

What is the React Compiler?

CARD 12 · QUESTION

What is the <Activity> component (19.2)?

CARD 13 · QUESTION

What does useEffectEvent do (19.2)?

CARD 14 · QUESTION

Name three smaller React 19 quality-of-life changes.

CARD 15 · QUESTION

Which headline features are still NOT stable in 19.2?

CARD 16 · QUESTION

Interview one-liner: what's the architectural theme of React 19?

React 19 flashcards — answers (cards 9-16)Columns mirrored so answers align with question backs
CARD 10 · ANSWER

Render them anywhere in a component and React hoists them to <head> automatically — native document metadata support, plus stylesheet and async script precedence handling.

CARD 9 · ANSWER

Nothing is needed anymore: in React 19, ref is a regular prop on function components. forwardRef is deprecated and codemods remove it.

CARD 12 · ANSWER

Wraps UI with modes 'visible' and 'hidden'. Hidden trees keep their state but unmount effects and render at low priority — ideal for tabs or pre-rendering likely-next screens.

CARD 11 · ANSWER

A build-time compiler (stable 1.0, late 2025) that auto-memoizes components and values by understanding the Rules of React — retiring most manual useMemo, useCallback, and React.memo.

CARD 14 · ANSWER

Context used directly as a provider (<MyContext> instead of .Provider), ref callbacks can return cleanup functions, and hydration errors now show a single readable diff.

CARD 13 · ANSWER

Extracts the 'event' part of an effect so it always reads the latest props/state without being a dependency — eliminating stale closures and effects that re-fire too often.

CARD 16 · ANSWER

Work moves off the client and out of your hands: RSC shifts rendering to the server, Actions absorb form boilerplate, and the Compiler absorbs memoization — less JS shipped, less code to maintain.

CARD 15 · ANSWER

View Transitions and Fragment Refs — real and demoed, but only in Canary/Experimental channels. Saying they're stable in an interview is a red flag.