UnhandledPromiseRejectionWarning when async route handler gets rejected

Imagine you have a rejected promise as a result of processing the request, you get an UnhandledPromiseRejectionWarning. Wouldn’t it be ideal to catch that and send as a normal error, so that the error middleware can take care of that? With some code, imagine you have a get function like

async function get(req, res, next) {
  throw new Error('some error');
}

if I set this to handle my request it will throw an UnhandledPromiseRejectionWarning, but I believe in a perfect world this should be wrapped in something like

  try {
   await get(...);
  } catch (error) {
    next(error);
  }

That way I wouldn’t have to do this for every route I have. Is there any downside to it? Would you guys accept a PR for this?

[pjpsoares]

It works perfectly, I guess I missed that one in the configuration. Thank you and sorry for wasting your time! Cheers

[jsdevel]

https://github.com/kogosoftwarellc/open-api/tree/master/packages/express-openapi#argspromisemode