How do you handle errors in async event handlers if error boundaries miss them?
PICTURE THIS: ASYNC / PROMISE
Simple meaning
I wrap the await in try catch and set error state or show a toast.
WHY — React instead of guessing?
Why interviewers care about React:
question about React.
trade-offs, and what you would actually do on a Frontend project - not buzzwords.
Name the idea, why it exists, then one short example.
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:
- 1I wrap the await
in try catch and set error state or show a toast.
- 2I can rethrow during
render by storing the error and throwing in the next render if I want a boundary to catch it.
- 3For route-level failures I
prefer an error element in the router.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
I wrap the await in try catch and set error state or show a toast. I can rethrow during render by storing the error and throwing in the next render if I want a boundary to catch it.