Synchronous error handling in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is synchronous error handling in Express?

It is the process of catching and managing errors that happen immediately during the execution of route handlers or middleware, before any asynchronous code runs.

beginner

How do you throw a synchronous error inside an Express route?

You can use the throw keyword with an Error object inside the route handler function. Express will catch this error and pass it to the error-handling middleware.

intermediate

What happens if you throw an error synchronously in an Express route without a try-catch block?

Express automatically catches synchronous errors thrown in route handlers and forwards them to the error-handling middleware, so you don't need to use try-catch manually.

beginner

How do you define an error-handling middleware in Express?

An error-handling middleware is a function with four parameters: (err, req, res, next). Express calls it when an error is passed or thrown.

beginner

Why is synchronous error handling important in Express?

It helps keep your app stable by catching immediate errors and sending proper responses instead of crashing the server or leaving requests hanging.

What happens when you throw an error synchronously inside an Express route handler?

A You must use try-catch to handle it manually.

B The server crashes immediately.

C The error is ignored and the request continues.

D Express catches it and passes it to error-handling middleware.

Express automatically catches synchronous errors thrown in route handlers and forwards them to error-handling middleware.

Which of these is the correct signature for an Express error-handling middleware?

A (req, res, next)

B (err, req, res, next)

C (req, res)

D (err, req, res)

Error-handling middleware in Express must have four parameters: err, req, res, and next.

If you throw an error synchronously in Express, do you need to wrap it in try-catch to send a response?

A Yes, always use try-catch.

B Only if you want to log the error.

C No, Express handles it automatically.

D Only for asynchronous errors.

Express automatically catches synchronous errors and passes them to error-handling middleware.

What is the main benefit of synchronous error handling in Express?

A It prevents the server from crashing and sends error responses.

B It speeds up the server response time.

C It automatically fixes bugs in the code.

D It logs errors to the console only.

Synchronous error handling helps keep the server stable by catching errors and sending proper responses.

Where should you place your error-handling middleware in an Express app?

A After all other routes and middleware.

B Before any routes.

C In the middle of route definitions.

D It does not matter.

Error-handling middleware should be placed after all routes and other middleware to catch errors from them.

Explain how synchronous errors are handled in Express and how you can define middleware to catch them.

Think about what happens when you throw an error inside a route function.

Describe why synchronous error handling is important in an Express application.

Consider what happens if errors are not caught.

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