New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this library needed when using express-async-handler or express-async-router? #36
Comments
In a way yes, this library like those you’ve mentioned aims to solve the same problem - not having to manually catch rejected promises in middlewares and send err to global handler.
|
2 more cents/FYIs here:
Our story: after upgrading Express and TS, we had to stop using express-async-errors and switched to express-async-handler; to do so, we had to apply the work-around for no-misused-promises eslint rule mentioned above. |
@kronicker JFYI, if you couple express-async-errors with TS typing which allows async handlers to be passed to express router matcher/handler (recent Express enforces all the handlers to return
|
https://www.npmjs.com/package/express-async-handler
https://www.npmjs.com/package/express-async-router
It sounds like using of one of the above libraries makes the usage of express-async-handler non-needed. Is it correct?
The text was updated successfully, but these errors were encountered: