How does `try...catch` work in JavaScript?

Q: How does `try...catch` work in JavaScript?

**Target Audience:** Engineers preparing for JavaScript error-handling interview questions. **Difficulty:** Easy > **How to read this doc:** Concepts are explained in plain language first, then tagged with 📌 Interview term: . Every result below was actually run on Node.js v24.19.0 — the printed output is real, captured output, not illustrative sample text. ## 1. Why This Even Matters — A Story First Think of a factory floor with a trip wire around one risky machine. If nothing goes wrong, workers walk past the wire and continue on to the next station without incident. If something DOES go wrong at that machine, the trip wire immediately redirects everyone straight to a designated recovery station -- skipping whatever else was left to do at the risky machine. And no matter which path was taken, a safety inspector always walks the floor at the very end of the shift, success or failure. try is the risky machine, catch is the recovery station, and finally is the safety insp

The problem

Question presented to candidate: "Walk me through exactly how try, catch, and finally work in JavaScript -- including a case or two where the behavior might surprise someone."

What a strong answer should cover:

try wraps code that might throw; if anything inside it throws, control jumps straight to catch with the thrown value, skipping the rest of the try block entirely.
finally always runs -- on the success path, on the caught-error path, and even if try or catch contains a return statement.
A genuinely surprising, verified edge case: a return statement inside finally overrides whatever try or catch already returned.
try...catch only catches synchronous throws inside the try block, and a rejected promise that is explicitly awaited inside it -- it does NOT catch a throw from inside a setTimeout callback or an unawaited async function, since those run on a later turn, after the try block has already finished.
Since ES2019, catch can be written with no bound parameter (catch { ... }) when the error value itself is not needed.

Clarifying questions expected:

"Should I focus on synchronous error handling, or also cover how it interacts with async/await and promise rejections?"

Code / implementation expected: Yes -- a short, runnable snippet demonstrating a caught sync throw, finally always running, and an awaited rejection being caught.

error handling
try/catch
exceptions
control flow

Try it yourself

Sketch your approach before you read the solution. That is what the interview tests.

Stuck? Get a hint.

A short nudge toward the approach. It will not give the answer away.

Solution

Target Audience: Engineers preparing for JavaScript error-handling interview questions. Difficulty: Easy

How to read this doc: Concepts are explained in plain language first, then tagged with 📌 Interview term:. Every result below was actually run on Node.js v24.19.0 — the printed output is real, captured output, not illustrative sample text.

1. Why This Even Matters — A Story First

Think of a factory floor with a trip wire around one risky machine. If nothing goes wrong, workers walk past the wire and continue on to the next station without incident. If something DOES go wrong at that machine, the trip wire immediately redirects everyone straight to a designated recovery station -- skipping whatever else was left to do at the risky machine. And no matter which path was taken, a safety inspector always walks the floor at the very end of the shift, success or failure.

The solution is hidden so you can try first

8 min read · 10 sections

Run the code

Edit the code and run it here. Each console line with an expected value becomes a test.

JavaScripttry/catch/finally, optional catch binding, finally overriding a return, awaited rejection (run directly)