u/sonemonu

just dropped v0.8.0 of UQL, with one of the most requested features: Decorator-Free Entity Definitions. So not everyone wants (or can) use experimentalDecorators in their tsconfig.json. This is common in certain edge runtimes, specific build pipelines, or simply for developers who prefer a more functional or imperative style.

With the new defineEntity API, you can now register your database entities entirely through code. This new approach is 100% compatible with envs where decorators are disabled or unsupported.

Check out the new syntax:

import { defineEntity } from 'uql-orm';

// No decorators, no tsconfig magic required!
class User {}

defineEntity(User, {
  name: 'users',
  fields: {
    id: { type: 'uuid', isId: true },
    name: { type: String },
    email: { type: String },
  },
  indexes: [
    { columns: ['name'] },
    { columns: ['email'], unique: true },
  ],
});

From u/sooodooo's comment in a past post we did, we got the idea about adding native support for new Bun SQL, so you don't need to install any additional dependencies when using UQL on Bun.

What we shipped:

• One native Bun path across SQL engines: Bun SQL unifies PostgreSQL/MySQL/SQLite under one API
  • UQL makes it cleaner because we abstract the SQL dialects with our Universal API so your app code stays consistent as you switch engines (Bun SQL docs).
• Same entity-first API/migrations flow as the rest of UQL
• No extra pg / mysql2 / better-sqlite3 install for Bun SQL usage
• Operational simplicity: one runtime, one SQL client model, one ORM API means less cognitive load for full-stack teams.

The hard part wasn't "connecting"; it was making behavior consistent across drivers (JSON, arrays, result normalization, migration safety, etc.) so the apps code stays portable across all the drivers and DBs.

Bun SQL guide: uql-orm.dev/bun-sql
Changelog details: GitHub changelog