MikroORM

TypeScript Data Mapper ORM for Node.js, with Unit of Work and Identity Map.

Created by @B4nan.

[MikroORM @MikroORM]

I just released v7.1.3, which includes several new opt-outs of the new v7.1 features like triggers and routines. This should ease adoption for those who were already using those db features before the ORM became aware of them.

If you face any kind of issue during upgrade, please let me know!

https://t.co/BwAro1g1CJ

[PowerSync @powersync_]

In this fun video, Steven shows us how he created an experimental @MikroORM integration.

For existing MikroORM users, PowerSync provides partial sync at scale: keep on-device SQLite synced with your backend database. PowerSync is designed for offline, real-time, and reactive use cases.

For existing PowerSync users, you might want to check out MikroORM as another great option. From what we can tell, the latest version probably works on React Native and Web too.

[MikroORM @MikroORM]

MikroORM 7.1 is out 🚀
- LazyRef<T>
- per-parent collection limiting
- PGlite driver
- query cancellation via AbortSignal
- database triggers
- stored procedures
- typed Kysely for NestJS/DI setups
- PostgreSQL partitioning

and more...

Blog post: https://t.co/lQi7dwTLMG
Changelog: https://t.co/22Os6zaOHg

[Tanner Linsley @tannerlinsley]

If AI reading your open source code hurts your business, you were likely using "open source" as a growth strategy instead of a philosophy. And closing it now doesn't make you secure. It just means fewer good-faith developers hardening your code, and more bad actors pointing AI at your production servers.

[Peter Steinberger 🦞 @steipete]

Managing open source is way harder than managing [paid] closed source projects.

At work, you have authority.
With OSS you have GitHub Issues.

[MikroORM @MikroORM]

@ericjeker God knows, consistency, I guess. Or maybe people started slowly adopting v7 after the first RCs went out?

[MikroORM @MikroORM]

After a year of stagnation, the downloads are finally growing nicely!

[Addy Osmani @addyosmani]

I can't remember the last time I was truly stuck on a coding problem. AI agents changed this. Going from "sometimes blocked" to "always moving" is wild.

[basarat @basarat]

TypeScript 6 is out!

Best change in my opinion: strict is true by default 🌹🎉

[MikroORM @MikroORM]

And v7.1 is shaping up already...

https://t.co/mdwkaUXxuA

[MikroORM @MikroORM]

MikroORM 7.0.5 is out!

https://t.co/FDCjZtZhfb

[MikroORM @MikroORM]

MikroORM 7.0.4 is out!

https://t.co/cm5a5GIF56

[MikroORM @MikroORM]

MikroORM 7.0.3 is out!

https://t.co/tZIkqpvSrs

[MikroORM @MikroORM]

@romainlanz https://t.co/Cq3k0YF14s

[MikroORM @MikroORM]

Also, AdonisJS guide just landed:

https://t.co/eDsWB9IkTk

[MikroORM @MikroORM]

MikroORM 7.0.2 is out!

If you wanted to use the new @vitest_dev 4.1, be sure to update, as there were some issues with the path detection caused by the new OXC runtime, which are now fixed.

https://t.co/uWO78AWfyh

[MikroORM @MikroORM]

@ZeldriFR And of course, kysely QB is available, and fully type safe (working with the entity types from the ORM).

https://t.co/imnYuD8OeD

[MikroORM @MikroORM]

MikroORM v7 is here. Zero deps, knex replaced with Kysely, native ESM, type-safe QB, polymorphic relations, Oracle support, and too many things to fit in a tweet.

https://t.co/4kjxw60jce

🧵👇

[MikroORM @MikroORM]

@ZeldriFR It would be quite a lot of work, their philosophy is WYSIWYG, in other words, different dialects require different constructs. I've spent a lot of time doing this with knex.js back in the day (v3), and I hated myself for that for years. I want to have absolute control.

[Vitest @vitest_dev]

Vitest 4.1 is out! 🚀

✅ Vite 8 support from day 1
🏷️ Test tags to organize, filter &amp; apply shared options
🪝 New hooks for easier tracing, transactions and AsyncLocalStorage
🔍 Async leak detection
🤖 Agent reporter to reduce token usage

And much more!