Synchronous error handling in Express - Step-by-Step Execution

Concept Flow - Synchronous error handling

Request received

↓

Route handler starts

↓

Code runs synchronously

↓

Error occurs?

No→Send response

Yes↓

Throw error

↓

Express catches error

↓

Error-handling middleware runs

↓

Send error response

This flow shows how Express handles errors thrown synchronously inside route handlers by passing them to error middleware.

Execution Sample

Express

app.get('/test', (req, res) => {
  if (!req.query.name) {
    throw new Error('Name required');
  }
  res.send(`Hello ${req.query.name}`);
});

This code throws an error synchronously if the 'name' query is missing, which Express catches and forwards to error middleware.

Execution Table

Step	Action	Condition	Result	Next
1	Request to /test without name query	N/A	Route handler starts	Check if name exists
2	Check if req.query.name exists	req.query.name is undefined	Condition true (missing)	Throw error
3	Throw new Error('Name required')	Error thrown	Express catches error	Pass to error middleware
4	Error-handling middleware runs	Receives error	Sends error response to client	End
5	Request to /test with name query	N/A	Route handler starts	Check if name exists
6	Check if req.query.name exists	req.query.name is present	Condition false	Send greeting response
7	Send res.send(`Hello ${req.query.name}`)	Response sent	Client receives greeting	End

💡 Execution stops after sending response or error response to client.

Variable Tracker

Variable	Start	After Step 2	After Step 6	Final
req.query.name	undefined or string	undefined (error path) or string (success path)	string (success path)	unchanged
error	none	Error('Name required') thrown	none	none

Key Moments - 2 Insights

Why does throwing an error inside the route handler not crash the server?

Express automatically catches synchronous errors thrown in route handlers and passes them to error-handling middleware, as shown in execution_table steps 3 and 4.

What happens if the error-handling middleware is missing?

Without error middleware, Express will send a default error response, but the server stays running. The error is still caught internally, preventing a crash.

Visual Quiz - 3 Questions

Look at the execution table, what happens at step 3 when the error is thrown?

A The server crashes immediately

B The request is ignored

C Express catches the error and passes it to error middleware

D The response is sent successfully

💡 Hint

Check the 'Result' column in step 3 of the execution_table

At which step does the route handler send a successful greeting response?

A Step 7

B Step 6

C Step 4

D Step 2

💡 Hint

Look for 'Send res.send' action in the execution_table

If req.query.name is missing, which step shows the error being handled?

A Step 2

B Step 4

C Step 1

D Step 7

💡 Hint

Find where error-handling middleware runs in the execution_table

Concept Snapshot

Synchronous error handling in Express:
- Throw errors inside route handlers synchronously.
- Express catches these errors automatically.
- Errors go to error-handling middleware.
- Middleware sends error response.
- Server stays running safely.

Full Transcript

In Express, when a route handler runs, it executes code synchronously. If an error is thrown inside this code, Express catches it automatically. This prevents the server from crashing. The error is passed to special error-handling middleware, which sends an error response to the client. If no error occurs, the handler sends a normal response. This flow ensures safe and clear error handling for synchronous code.

Practice

1. In Express, how do you handle synchronous errors inside a route handler?

easy

A. Use setTimeout to catch errors asynchronously

B. Use async/await without try...catch

C. Ignore errors and let the server crash

D. Use a try...catch block and call next(error) inside catch

Solution

1. Step 1: Understand synchronous error handling

   Synchronous errors happen immediately and can be caught with try...catch blocks.

2. Step 2: Pass error to Express error handler

   Inside catch, call next(error) to forward the error to Express's error middleware.

3. Final Answer:

   Use a try...catch block and call next(error) inside catch -> Option D

4. Quick Check:

   try...catch + next(error) = A [OK]

Hint: Catch sync errors with try...catch and call next(error) [OK]

Common Mistakes:

• Not using try...catch for synchronous errors
• Calling next() without an error object
• Using async/await without try...catch for sync errors

2. Which of the following is the correct syntax to pass a synchronous error to the next middleware in Express?

easy

A. next(new Error('Something went wrong'))

B. throw new Error('Something went wrong')

C. res.send(new Error('Something went wrong'))

D. console.error('Something went wrong')

Solution

1. Step 1: Identify how to forward errors in Express

   Express expects errors to be passed to next() as an argument to trigger error middleware.

2. Step 2: Check syntax correctness

   Calling next(new Error('...')) correctly passes the error object to Express.

3. Final Answer:

   next(new Error('Something went wrong')) -> Option A

4. Quick Check:

   next(error) syntax = B [OK]

Hint: Use next(error) to forward errors in Express [OK]

Common Mistakes:

• Throwing error without try...catch in sync code
• Sending error object in response instead of next()
• Logging error without forwarding it

3. What will be the output when this Express route is called?

app.get('/test', (req, res, next) => {
  try {
    throw new Error('Fail');
  } catch (err) {
    next(err);
  }
});

app.use((err, req, res, next) => {
  res.status(500).send(err.message);
});

medium

A. The server crashes with uncaught exception

B. The client receives a 200 status with empty body

C. The client receives a 500 status with message 'Fail'

D. The client receives a 404 Not Found error

Solution

1. Step 1: Analyze error throwing and catching

   The route throws an error inside try, caught immediately, then passed to next(err).

2. Step 2: Understand error middleware response

   The error middleware sends a 500 status with the error message 'Fail' to the client.

3. Final Answer:

   The client receives a 500 status with message 'Fail' -> Option C

4. Quick Check:

   next(err) triggers error middleware = A [OK]

Hint: Errors passed to next() trigger error middleware response [OK]

Common Mistakes:

• Assuming error crashes server without middleware
• Expecting 200 status despite error
• Confusing error middleware with normal middleware

4. Identify the error in this Express route for synchronous error handling:

app.get('/error', (req, res, next) => {
  throw new Error('Oops');
  next();
});

medium

A. No error, code works fine

B. Error is thrown but not caught or passed to next()

C. Error middleware is missing

D. next() is called after throw, which is unreachable

Solution

1. Step 1: Check error throwing without try...catch

   The error is thrown synchronously but not caught, so Express cannot handle it properly.

2. Step 2: Understand consequence of uncaught error

   Without try...catch and calling next(err), the server may crash or not handle error gracefully.

3. Final Answer:

   Error is thrown but not caught or passed to next() -> Option B

4. Quick Check:

   Throw without catch + next(err) = D [OK]

Hint: Always catch sync errors and call next(error) [OK]

Common Mistakes:

• Throwing error without try...catch
• Calling next() after throw (unreachable code)
• Assuming Express auto-catches thrown errors

5. You want to handle synchronous errors in multiple routes without repeating try...catch blocks. Which Express feature helps you achieve this cleanly?

hard

A. Create a wrapper function that catches errors and calls next(err)

B. Use setTimeout to delay error throwing

C. Call res.end() immediately to avoid errors

D. Use global variables to store errors

Solution

1. Step 1: Recognize repetitive try...catch problem

   Wrapping every route in try...catch is repetitive and cluttered.

2. Step 2: Use a wrapper function to centralize error catching

   A wrapper function can run the route handler and catch sync errors, forwarding them with next(err).

3. Final Answer:

   Create a wrapper function that catches errors and calls next(err) -> Option A

4. Quick Check:

   Wrapper function for sync error handling = C [OK]

Hint: Use wrapper functions to catch and forward sync errors [OK]

Common Mistakes:

• Trying to delay errors with setTimeout
• Ignoring errors by ending response early
• Using global variables for error handling