Lifecycle of reactive Effects in code
useEffect(() => {
const connection = connect(roomId);
return () => connection.disconnect();
}, [roomId]);Read the example from data and control flow to the resulting UI. Keep the component boundary small.
Back to week 2
Topic
Lifecycle of reactive Effects
Definition
An Effect has an independent setup-cleanup lifecycle that starts after commit and restarts whenever its dependencies change.
In simpler words
Think of an Effect as connecting and disconnecting from something outside React as its inputs change.
Setup, cleanup, dependency changes, and unmount.
After this you can
- Prevent leaks and stale connections.
- Explain the trade-off to a teammate using a small example.
- Name at least one common bug pattern for this topic.
Understand Lifecycle of reactive Effects
Setup, cleanup, dependency changes, and unmount.
Start by identifying which value or browser behavior changes. Then describe the UI from that current input instead of editing the DOM as a separate source of truth.
Apply Lifecycle of reactive Effects
Keep rendering as a calculation. Put user-triggered changes in event handlers, preserve UI memory in state, and reserve external synchronization for Effects or the server-state layer.
Name values by their UI meaning, test the loading and error path when data is remote, and avoid keeping two editable copies of the same value.
Ask before adding code: is this local UI memory, shared client state, or Nest-owned server state?
Where bugs hide
Definition
High-bug areas are places where a small API misuse looks correct but produces stale UI, duplicate work, or silent failures.
In simpler words
Each mistake below shows Wrong vs Right code — compare them side by side.
When something misbehaves, match the symptom to a pattern below before rewriting the feature.
Prefer fixing the ownership or update path over adding another Effect or sync step.
Mistake: No cleanup on dep change
// Wrong
useEffect(() => { connect(roomId); }, [roomId]);
// Right
useEffect(() => {
const c = connect(roomId);
return () => c.disconnect();
}, [roomId]);Disconnect before reconnecting.
Mistake: Disable exhaustive-deps
// Wrong
// eslint-disable-next-line react-hooks/exhaustive-deps
// Right
// restructure: updater form, split Effects, or move logic to eventsSilencing the linter hides stale bugs.
Mistake: Measure layout in useEffect only
// Wrong
useEffect(() => setH(ref.current!.offsetHeight), []);
// Right
useLayoutEffect(() => setH(ref.current!.offsetHeight), []);Use layout Effect when you must measure before paint.
Live playground
Lifecycle of reactive Effects sandbox
Change one input at a time and predict the next render.
tick = 0
Keep in mind
- Keep the formal definition in mind; it explains which tool belongs where.
- Prefer one source of truth over synchronized copies of the same value.
- When behavior surprises you, trace: input → update → render → committed UI.
- Study the Wrong vs Right examples in “Where bugs hide” before you merge.
Test
Check your understanding
At least 10 questions — mix of concept, syntax, practical, and logic. Score ≥ 80% (enforced by the API) to save progress.
Checking your session…
10 questions · concept 3 · syntax 3 · practical 2 · logic 2