High React Question 146 of 229

How would you avoid stale closures in hooks?

Frontend Master · Speak this in 60–90 seconds · Faridabad & Delhi NCR

PICTURE THIS: ARRAY IN MEMORY

01234

Index starts at 0. Scan once for max — O(n).

Simple meaning

I include the value in the dependency array, or I read it from a ref that I update every render.

WHY — React instead of guessing?

Why interviewers care about React:

This is a process

question about React.

Panels listen for order,

trade-offs, and what you would actually do on a Frontend project - not buzzwords.

Stay structured

Name the idea, why it exists, then one short example.

Close cleanly

End with when you use it and one common pitfall.

STEPS — What happens step by step?

Before you speak the answer, walk the interviewer through these steps:

1
I include the value
in the dependency array, or I read it from a ref that I update every render.
2
Functional state updates avoid
stale state in event handlers.
3
For event listeners I
often keep a ref to the latest callback so I do not re-subscribe every keystroke.
4
Give an example
One tiny concrete case you can say aloud.
5
Common mistake
What juniors usually get wrong.
6
Close
When you pick this over the alternative.

EXAMPLE — See it in action

Here's a short line you can speak, broken into clear beats:

Say this line

“Functional state updates avoid stale state in event handlers.”

Break into beats

Functionalstateupdatesavoidstalestate

Speaking order

2987408337471632900

Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.

Key takeaway

I include the value in the dependency array, or I read it from a ref that I update every render. Functional state updates avoid stale state in event handlers.