DEV Community

Are You Bored of Try Catch😒

Nurul Islam Rimon on March 01, 2025

Handling Errors in Express with a Custom catchAsync Middleware When building web applications using Express, error handling is one of the most cruc...

Read full post

genix • Mar 1

The approach in this article is great, but it’s not always the best solution. While wrapping async functions with catchAsync removes repetitive try-catch blocks, it still ties error handling to Express’s middleware flow. This means that if you need more control over error propagation, custom error reactions, or want to handle errors outside the typical HTTP request cycle, this pattern can feel limiting.

In contrast, with Gland you can leverage its event-driven nature to decouple error handling from the core logic. Instead of just using try-catch, you could emit an error event like so:

try {
  // some code
} catch (e) {
  ctx.emit("handler:error", ctx);
}

This gives you the flexibility to manage errors in a more modular way, which can be especially useful in complex systems. Overall, while the catchAsync pattern works well for many Express applications, using an event-based approach like in Gland can offer a more adaptable solution depending on your project’s needs.

Nurul Islam Rimon • Mar 4 • Edited

Thanks, Genix💚
It will be very helpful for me.

Reid Burton • Mar 2

I want the tc39 for the const[error, resp] ?= await(response); format to go through.

Lara Stewart - DevOps Cloud Engineer • Mar 3

I'm also waiting on this. 🫤

Nurul Islam Rimon • Mar 4

Thank Reid Burton!

Vitaliy Potapov • Mar 2

The article makes a great point! For a more general approach, there's a try operator proposal for JavaScript that will hopefully reduce the need to write try-catch blocks as often.