RepoSense RS Monogram
RepoSensereposen.se
/llm.txtGitHub Repo
mikro-orm icon

mikro-orm/mikro-orm

v7.2.8

Curated database / backend repository (mikro-orm/mikro-orm) tracked via conditional GitHub .atom polling.

COMPATIBLE
What is mikro-orm/mikro-orm?

MikroORM is a TypeScript-first Object-Relational Mapper (ORM) based on the Data Mapper and Unit of Work patterns for SQL and NoSQL databases. It eliminates the manual work of writing raw queries and synchronizing database changes by tracking entity state transitions automatically. This enables backend engineers to write clean, maintainable domain models without coupling business logic to underlying storage drivers.

DATABASEnpm:@mikro-orm/coreTypeScriptreleases.atom
9,270+14 stars (24h)
#mikro-orm#typescript
AI Executive Summary & Artifact Size Impact
Quick Summary: What Changed · What To Do · Upgrade Effort

Fixes query caching keys, default ordering, and driver dialect bugs. Safe drop-in upgrade. Migration: None.

Semver: PATCH·Manifest: package.json
Artifact Size Impactunavailable
Size Unavailable
Telemetry unmeasured for pre-release or source-only registry build
Breaking Changes, Release Highlights & Migration Snippet

Key Release Highlights (v7.2.8)

  • Applies configured entity default orderBy definitions automatically during em.stream() and em.findOne() operations.
  • Fixes query cache and dataloader key generation to safely serialize regex patterns, raw SQL fragments, and non-JSON values.
  • Improves entity serialization performance by isolating context propagation solely to the serialized object path.
  • Corrects SQL dialect edge cases, including table partitioning persistence in schema snapshots and composite relation sorting in paginated queries.
Zero Breaking Changes Detected

Verified safe drop-in upgrade for @mikro-orm/core in package.json.

Copy-Paste Upgrade / Migration Snippet
npm install @mikro-orm/core@7.2.8 @mikro-orm/cli@7.2.8

Ecosystem Compatibility Matrix & Verified Graph Warnings

TypeScript >=5.0compatible— Full support for strict typing, entity metadata inference, and relation mapping.
Node.js >=18.12compatible— Verified compatible with Active and Maintenance LTS Node.js environments.
MongoDB >=5.0compatible— Resolves $re regex conversions in $elemMatch and fixes inverse M:N populate limits.

Zero-Noise Historical Release Timeline (2)

Format: [Core Change] + [Required Action] + [Migration Effort]
v7.2.8COMPATIBLE⚖️ Size Unavailable

Fixes query caching keys, default ordering, and driver dialect bugs. Safe drop-in upgrade. Migration: None.

v7.2.7COMPATIBLE⚖️ Size Unavailable

core: don't convert a sub-query value with the property's. Drop-in upgrade. Migration: None.

Upgrade & Migration Q&A (mikro-orm/mikro-orm v7.2.8)

Direct Answers for Engineers & AI Agents

Is mikro-orm/mikro-orm v7.2.8 safe to upgrade in production?

mikro-orm/mikro-orm v7.2.8 is classified as COMPATIBLE (PATCH release). Fixes query caching keys, default ordering, and driver dialect bugs. Safe drop-in upgrade. Migration: None.

What breaking changes or compatibility risks exist in mikro-orm/mikro-orm v7.2.8?

No breaking API changes or peer dependency conflicts are recorded for mikro-orm/mikro-orm v7.2.8 in the RepoSense compatibility graph.

What is the bundle size impact of @mikro-orm/core v7.2.8?

Measured bundle size telemetry is currently unavailable for @mikro-orm/core v7.2.8; verify build output locally before deploying.

How do I upgrade @mikro-orm/core to v7.2.8?

Upgrade @mikro-orm/core to v7.2.8 by running "npm install @mikro-orm/core@7.2.8" and applying the migration steps: npm install @mikro-orm/core@7.2.8 @mikro-orm/cli@7.2.8