Skip to content

Glossary · 24 terms

React

Components, hooks, rendering and server components.

Beginner · Students and graduates

Component
The building block of a React app: a JavaScript function that takes props and returns JSX describing what to show. Read the reference
Props
Read-only values passed into a component like HTML attributes. A component should never change its own props. Read the reference
State
Values a component keeps with useState. Setting state schedules a re-render with the new value. Read the reference
JSX
A syntax extension that compiles to function calls creating React elements. Curly braces embed JavaScript expressions. Read the reference
Hook
Functions like useState and useEffect that let components use state and other features. Call them at the top level only. Read the reference
Render
Rendering calls your component to get JSX. React then compares it with the last result and updates only what changed in the DOM. Read the reference
Fragment
Written as <>…</>, it lets a component return several elements side by side without an extra div. Read the reference
Key
A stable, unique key on each item in a list lets React keep the right state with the right item when the list changes. Read the reference

Practitioner · Working engineers

useEffect
Runs code after render to connect to external systems, such as subscriptions or timers, with a cleanup when dependencies change. Read the reference
Context
createContext and useContext let a provider share a value with any component below it, such as a theme or the current user. Read the reference
Reducer
With useReducer, all the update logic lives in one pure function, which keeps complex state changes predictable. Read the reference
Memo
memo wraps a component so React reuses the last result if props are equal. useMemo caches a computed value the same way. Read the reference
Ref
useRef gives a mutable object that persists across renders. It’s used for DOM nodes, timers and other values the UI doesn’t show. Read the reference
Portal
createPortal renders into another place in the DOM, such as document.body for modals, while staying in the React tree. Read the reference
Suspense
A boundary that displays fallback content until the components inside it are ready, such as lazy code or data. Read the reference
Hydration
The client renders the same tree over server HTML and attaches event handlers, so the page becomes interactive without re-creating the DOM. Read the reference

Lead · Seniors and managers

Fiber
React’s internal data structure for one component instance. Work on fibers can be split, paused and prioritised. Read the reference
Reconciler
Reconciliation compares the new element tree with the previous one and computes the minimum set of changes to apply. Read the reference
Transition
startTransition and useTransition mark state updates as interruptible, so urgent updates like typing are handled first. Read the reference
Actions
Functions passed to a form’s action or run in a transition. React tracks their pending state, errors and optimistic updates. Read the reference
RSC
React Server Components render ahead of time on the server, can read data directly, and add nothing to the client bundle. Read the reference
Use
use(resource) reads the value of a promise or a context. Unlike hooks, it can be called inside conditions and loops. Read the reference
Compiler
React Compiler analyses components and inserts memoization for you, so manual useMemo and useCallback are rarely needed. Read the reference
Streaming
The server flushes the page shell first and fills in Suspense boundaries as their data resolves, so users see content sooner. Read the reference