Why must you handle unhandledRejection on a Node server?
PICTURE THIS: 1, 2, 2, 8
Simple meaning
An unhandled promise rejection means async work failed with no catch.
WHY — Node.js instead of guessing?
Why interviewers care about Node.js:
on Node.js.
the situation, the default choice, and one exception - that reads as experience.
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:
- 1An unhandled promise rejection
means async work failed with no catch.
- 2Depending on Node version
and flags, it can log and continue or crash the process.
- 3Crash-and-restart is often safer
than serving a process whose state is unknown.
- 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
An unhandled promise rejection means async work failed with no catch. Depending on Node version and flags, it can log and continue or crash the process.