turbine-orm 0.28.0 → 0.28.1

package/README.md

@@ -990,13 +990,13 @@ Turbine is focused and opinionated. Here's what it doesn't do:
 
 ## Requirements
 
-- Node.js >= 18.0.0
+- Node.js >= 20.0.0
 - PostgreSQL >= 14
 - Works with both ESM (`import`) and CommonJS (`require`)
 
 ## Contributing
 
-Contributions are welcome. See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, the test strategy, and the PR checklist. The unit suite runs without a database:
+Contributions are welcome. See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, the test strategy, and the PR checklist. Participants agree to the [Code of Conduct](CODE_OF_CONDUCT.md). The unit suite runs without a database:
 
 ```bash
 npm install

package/dist/cjs/errors.js

@@ -30,11 +30,25 @@ exports.TurbineErrorCode = {
     EXCLUSION_VIOLATION: 'TURBINE_E016',
     UNSUPPORTED_FEATURE: 'TURBINE_E017',
 };
+/**
+ * Prefix a human message with its stable error code so logs are greppable
+ * without requiring structured field access. Idempotent if the message already
+ * starts with `[TURBINE_E0NN]`.
+ */
+function formatErrorMessage(code, message) {
+    const tag = `[${code}]`;
+    if (message.startsWith(tag))
+        return message;
+    // Empty message → just the code (defensive; callers always pass text today).
+    if (!message)
+        return tag;
+    return `${tag} ${message}`;
+}
 /** Base error class for all Turbine errors */
 class TurbineError extends Error {
     code;
     constructor(code, message, options) {
-        super(message, options);
+        super(formatErrorMessage(code, message), options);
         this.name = 'TurbineError';
         this.code = code;
     }

package/dist/cjs/powdb.js

@@ -10,7 +10,7 @@
  * seam. The four SQL engines are untouched.
  *
  * PowDB realities shape the design (all verified firsthand against a live
- * `powdb-server` / the embedded addon, see `docs/strategy/powdb-parity-matrix.md`):
+ * `powdb-server` / the embedded addon, see `docs/internal/strategy/powdb-parity-matrix.md`):
  *   - **`RETURNING` (since 0.7.0)** — `create/createMany/update/delete` append the
  *     trailing `returning` keyword (`RETURNING *`, all columns) and read the
  *     affected rows back in one round-trip. `upsert` is the lone exception (its

package/dist/cjs/powql.js

@@ -11,7 +11,7 @@
  * it separate also means the four SQL engines are untouched.
  *
  * Behavioural deltas from the SQL path, all driven by PowDB's wire reality (see
- * `docs/strategy/powdb-parity-matrix.md`, every row verified against a live
+ * `docs/internal/strategy/powdb-parity-matrix.md`, every row verified against a live
  * server):
  *   - `create`/`createMany`/`update`/`delete` use PowDB 0.7.0's trailing
  *     `returning` keyword (`RETURNING *`, all columns) to surface affected rows