There are already a lot of ORMs for node.js with different strong and weak sides, but still, this is not enough, there is still not a single tool to cover typical needs simultaneously:

Type safety

Flexibility

Easiness of use for more complex cases...

Dennis Chiroro

Erlang

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Announcing Orchid ORM, a new TypeScript ORM that offers type safety, flexibility, ease of use for complex cases, and performance. The ORM addresses the limitations of raw SQL and query builders and provides a more powerful and TypeScript-friendly alternative.

Announcing a new TypeScript ORM

Permalink Raw SQL vs query builders vs ORMs

Permalink Easiness of use for more complex cases

Hi,
please, have you tried it? Do you have any plus and cons from the real use case? For example in comparison to TypeORM.
Recently I have been deciding between TypeORM and Prisma and I have chose TypeORM because Prisma scheme cannot be split into multiple parts (and it started to bloat very quickly) and the TypeORM feels more like a Doctrine from PHP, supports splitting, migrations and seems ok, more “native” and the usage seems to me a bit more “straightforward”.

Looks interesting. I would love to see the code examples put next to the SQL that is generated in the end.

very interesting , starred &amp; bookmarked