Express doen't know how to handle async/await. If an error is thrown inside an async handler, instead of the error being handled correctly it throws an UnhandlesPromiseRejectionError in Node 15+ and can cause memory leaks in below versions
I've tried almost all framework (express,koa,nest,adonis,feathers,hapi,etc) and i think Express wins from them all by simplicity. I'm using express with/out Typescript for 5 years and it works very well with no issue. If you face UnhandlesPromiseRejectionError, you might not use try/catch in the first place. Yes, by default it doesn't handle that error. If you face some problems in Express, belive me it's not the framework fault, sometimes its dev lack of knowledges.
And for Romain Lanz article, mostly not true and he tends to drop Express because he is one of the Adonisjs contributor.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Express doen't know how to handle async/await. If an error is thrown inside an async handler, instead of the error being handled correctly it throws an UnhandlesPromiseRejectionError in Node 15+ and can cause memory leaks in below versions
I've tried almost all framework (express,koa,nest,adonis,feathers,hapi,etc) and i think Express wins from them all by simplicity. I'm using express with/out Typescript for 5 years and it works very well with no issue. If you face UnhandlesPromiseRejectionError, you might not use try/catch in the first place. Yes, by default it doesn't handle that error. If you face some problems in Express, belive me it's not the framework fault, sometimes its dev lack of knowledges.
And for Romain Lanz article, mostly not true and he tends to drop Express because he is one of the Adonisjs contributor.