Synchronizing with Effects in code
useEffect(() => {
const id = setInterval(tick, 1000);
return () => clearInterval(id);
}, []);Read the example from data and control flow to the resulting UI. Keep the component boundary small.
Back to week 2
Topic
Synchronizing with Effects
Definition
An Effect synchronizes a rendered component with an external system after React commits the DOM update.
In simpler words
Use an Effect for timers, subscriptions, browser APIs, or other work outside React’s render calculation.
useEffect setup, dependencies, and cleanup.
After this you can
- Write effects that start and stop external work safely.
- Explain the trade-off to a teammate using a small example.
- Name at least one common bug pattern for this topic.
Understand Synchronizing with Effects
useEffect setup, dependencies, and cleanup.
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 Synchronizing with 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: Missing interval cleanup
// Wrong
useEffect(() => {
setInterval(tick, 1000);
}, []);
// Right
useEffect(() => {
const id = setInterval(tick, 1000);
return () => clearInterval(id);
}, []);Cleanup prevents duplicate timers and leaks.
Mistake: Empty deps but reading props
// Wrong
useEffect(() => {
connect(roomId);
}, []); // roomId ignored
// Right
useEffect(() => {
const c = connect(roomId);
return () => c.disconnect();
}, [roomId]);List every reactive value the Effect reads.
Mistake: Fetch-only Effects for Nest lists
// Wrong
useEffect(() => { list().then(setTickets); }, []);
// Right
useQuery({ queryKey: ["tickets"], queryFn: list })Query owns loading/error/cache/invalidation.
Live playground
Synchronizing with Effects sandbox
Change one input at a time and predict the next render.
Seconds: 0
Cleanup clears the interval when stopped/unmounted.
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