TypeORM is in a bad place and we should probably drop it

[klm127]

I came across an issue on a TypeORM related package, typeorm-model-generator.

Link to Issue from Feb. 2021

typeorm-model-generator has been archived because the authors do not believe Typeorm is workable, and has too many problems.

I don't think typeorm should be considered as option for new projects other than prof of concepts or some workshop exercises. Typeorm is in a bad place. It's been like that for few years and I don't believe this will change any time soon(if ever). There are even some long standing bugs which can result in data loss. Some of the fixes are blocked by inability to introduce breaking changes - next branch(planned 0.3.0 version) has been with us for 3 years now and yet there are no concrete plans on releasing it or throwing that code away. I've decided to mark this project as maintenance only to make sure that any newcomers think twice before choosing typeorm for their ORM.

Some other ORM type libs were mentioned in the replies:

• knex (query builder, not an ORM)
• mikro-orm
• objectionjs
• prisma
• sequelize

Despite seeming to have pretty lengthy documentation, I certainly struggled with TypeORM. That it could risk losing data is highly concerning. It's early enough in the project that it won't be too difficult to change to another ORM technology. It might really only change the "DataSource" module.

TypeOrm currently has 1.9k issues including many bugs labeled triage which is concerning. I believe it's the right move to switch, just a matter of selecting what to switch to.

Any input appreciated.

[klm127]

It's prisma. Definitely prisma, as one of the comments in the model generator repo suggested. More mature and developed than any other of the repositories. Powerful stuff.

I switched the dependency and all related code over to Prisma so this issue is resolved.