Ranked in these QuestionsQuestion Ranking
Pro Written in TypeScript
Integrates very well with Angular projects and other projects leveraging TypeScript.
Pro No major contenders
May inexplicably have no major contenders in TS land.
Pro Weak Controller Generation and Discovery
Loopback and Sails implement API generation natively, with lots of features. TypeORM integrates Express route / endpoint / controller generation via an extension.
Loopback implements complex database discovery with SQL and NoSQL stores. TypeORM can also generate models based on an existing database, but it is done via extension and the database must be SQL: Microsoft SQL Server, PostgreSQL, MySQL, or MariaDB.
Still, these are great features most Node ORMs today do not have at all.
Pro Abstracts SQL and NoSQL
Able to connect to SQL and NoSQL sources with a unified API.
Con Confuses Classes with Types
Con Uncertain future
Confusing/obscure/unpredictable/broken parts. Sometimes glorious, sometimes goofy. Devs almost abandoned the project. Feels like driving a luxury car with flat tires.
Con Based on decorators
TypeORM relies on decorators, and obsolete implementations of them at that. To add insult to injury, simple decorator syntax is not provided. So you need to write e.g.
@Column() instead of
@Column. This is an issue with the API design, a very nasty one (Angular does it is not a good reason to do anything).