mikro-orm

After more than a year in development, MikroORM 6 gets stable today. It brings greatly improved types, with strict partial loading support. Here are a few highlights of what's inside: - strict partial loading [1] - new Getting Started guide [2] - reworked `Loaded` type and improved intellisense all over the place - implicit serialization now fully respects populate hints - polished joined strategy (new default) with support for `populateWhere: 'all'` - cursor-based pagination - reworked support for raw SQL fragments - $some, $none and $every subquery operators - dataloader support for Reference and Collection properties - improved logging support with logger context - extending EntityManager repo: https://github.com/mikro-orm/mikro-orm blog: https://mikro-orm.io/blog/mikro-orm-6-released [1] https://stackblitz.com/edit/mikro-orm-v6-strict

I support those, and I believe they deserve more: - SerenityOS [0], they do get some donations, but nothing close to the Linux Foundation, Wikipedia, or Mozilla. - MikroORM [1] if you'd like to support an ORM for TypeScript in the backend, again some donations, but nothing close to SerenityOS! [0]: https://github.com/SerenityOS/serenity [1]: https://github.com/mikro-orm/mikro-orm

Author said it isn't[0] a year ago but not sure. I think it allows a couple of strategies to be used. [0] https://github.com/mikro-orm/mikro-orm/issues/403

Please give MikroORM a shot, vastly better than the mentioned. https://github.com/mikro-orm/mikro-orm

Ha. Well, one of 'em was just fixed. https://github.com/mikro-orm/mikro-orm/issues/725 There's also a known issue where an insert statement with an `undefined` for a field (rather than the lack of a presence) translates to a null (this is actually a `pg` driver situation). https://github.com/mikro-orm/mikro-orm/issues/719 Finally, the docs have entities which use TypeScript's `optional` indicator (e.g. `image?: string`). Problem is, that reflects the state of an entity pre-creation. After creation it's going to be `null`, which will definitely escape the type system (you've got strict null checks on in TS, right?). However, typing that same column as `image: string | null` actually produces a `columnType` of JSONB(?) rather than `STRING NULL`. That's a couple examples, but yeah. I invested some heavy hours into the codebase this weekend.

MikroORM is TypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Key features: - Implicit transactions - ChangeSet based persistence - Supports both SQL and NoSQL website: http://mikro-orm.io/ repo: https://github.com/mikro-orm/mikro-orm release article (v3): https://mikro-orm.io/blog/mikro-orm-3-released introductory article (v2): https://mikro-orm.io/blog/introducing-mikroorm-typescript-da...

If you go the JS/TS route, definitely go with MikroORM as your ORM [1]... it is rather newish, but works unlike all other JS/TS ORM's on the open source market. Namely it has implemented Unit of Work... [1] https://github.com/mikro-orm/mikro-orm (Note: v3 is beta and what you should start with. Quite stable as it has 100% coverage.)