uql-orm 0.31.0 → 0.31.1

package/README.md

@@ -34,17 +34,16 @@ npm install uql-orm pg   # or mysql2, mariadb, better-sqlite3, mongodb, @tursoda
 
 That is the whole install ([setup](https://uql-orm.dev/getting-started)), and the [imperative API](https://uql-orm.dev/entities/imperative) skips decorators altogether.
 
-```ts
-await pool.findMany(User, {
-  $select: { id: true, email: true },
-  $populate: { posts: { $select: { title: true } } },
-  $where: { email: { $endsWith: '@uql-orm.dev' } },
-  $limit: 10,
-});
-```
+<a href="https://uql-orm.dev">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://uql-orm.dev/demo-dark.webp">
+    <img src="https://uql-orm.dev/demo-light.webp" alt="A UQL query being typed: the compiler underlines the misspelled 'emial', then 'titel' three levels deep inside $populate">
+  </picture>
+</a>
+
+Our type-safety automatically prevents the bugs above, without codegen: the entity classes are the schema, pure TypeScript power. That demo editor is [on the home page](https://uql-orm.dev).
 
-That query is a serializable value. Build it dynamically, store it, diff it, or send it
-from the browser to the server. The same object runs on every supported database.
+The query is just JSON: build it dynamically, store it, diff it, or send it from the browser to the server. The same object runs on every supported database.
 
 ## Why UQL?
 

package/package.json

@@ -3,7 +3,7 @@
   "homepage": "https://uql-orm.dev",
   "description": "JSON-native TypeScript ORM for Node.js, Bun and Deno. Supports PostgreSQL, PGlite, MySQL, MariaDB, SQLite, CockroachDB, Turso, Neon, Cloudflare D1 and MongoDB. Queries are plain JSON, typed to the leaf.",
   "license": "MIT",
-  "version": "0.31.0",
+  "version": "0.31.1",
   "type": "module",
   "engines": {
     "node": ">=24"