@btravstack/prisma 0.14.0 → 0.15.0

package/dist/index.cjs

@@ -6,8 +6,8 @@ let _prisma_adapter_pg = require("@prisma/adapter-pg");
 let unthrown = require("unthrown");
 //#region src/instrument.ts
 /**
-* Every query, wrapped: a span around it, a count of how it came out, and a log
-* line if it failed.
+* Every query, handed to the graph's observers: a count of how it came out, and
+* a log line if it failed.
 *
 * **This is why a generated client can be instrumented at all.** Prisma's
 * `$extends` takes a `query` component, and `$allModels.$allOperations`
@@ -16,10 +16,11 @@ let unthrown = require("unthrown");
 * revision of this package claimed instrumentation was impossible for that
 * reason; it was wrong, and this is the mechanism it missed.
 *
-* **It deliberately opens no span.** `@btravstack/prisma/otel` enables Prisma's
-* own `@prisma/instrumentation`, which traces at the ENGINE level — the real
-* SQL, the connection acquisition, the serialisation — all of it below what a
-* client-level wrapper can see. Emitting a span here as well would put two
+* **It deliberately opens no span.** Prisma's own `@prisma/instrumentation`,
+* which this package offers to `Instrumentations` and
+* `@btravstack/observability/otel` enables, traces at the ENGINE level — the
+* real SQL, the connection acquisition, the serialisation — all of it below
+* what a client-level wrapper can see. Emitting a span here as well would put two
 * spans on every query for strictly less information. What this wrapper keeps
 * is the pair Prisma's instrumentation does not do at all: a metric, and an
 * error line correlated with the ambient unit.
@@ -143,7 +144,7 @@ const prismaDatabase = (name) => ({ client }) => {
 		inject: { logger: _btravstack_core.Logger },
 		sync: ({ logger }) => () => loadPrismaInstrumentation(logger)
 	});
-	const chosen = (0, _btravstack_di.Module)(name)({
+	const database = (0, _btravstack_di.Module)(name)({
 		needs: [_btravstack_config.Env, _btravstack_core.Logger],
 		provides: [
 			config,
@@ -161,7 +162,7 @@ const prismaDatabase = (name) => ({ client }) => {
 			_btravstack_core.Instrumentations
 		]
 	});
-	return Object.assign(chosen, { port: DatabasePort });
+	return Object.assign(database, { port: DatabasePort });
 };
 //#endregion
 exports.prismaDatabase = prismaDatabase;

package/dist/index.mjs

@@ -5,8 +5,8 @@ import { PrismaPg } from "@prisma/adapter-pg";
 import { fromPromise, fromSafePromise } from "unthrown";
 //#region src/instrument.ts
 /**
-* Every query, wrapped: a span around it, a count of how it came out, and a log
-* line if it failed.
+* Every query, handed to the graph's observers: a count of how it came out, and
+* a log line if it failed.
 *
 * **This is why a generated client can be instrumented at all.** Prisma's
 * `$extends` takes a `query` component, and `$allModels.$allOperations`
@@ -15,10 +15,11 @@ import { fromPromise, fromSafePromise } from "unthrown";
 * revision of this package claimed instrumentation was impossible for that
 * reason; it was wrong, and this is the mechanism it missed.
 *
-* **It deliberately opens no span.** `@btravstack/prisma/otel` enables Prisma's
-* own `@prisma/instrumentation`, which traces at the ENGINE level — the real
-* SQL, the connection acquisition, the serialisation — all of it below what a
-* client-level wrapper can see. Emitting a span here as well would put two
+* **It deliberately opens no span.** Prisma's own `@prisma/instrumentation`,
+* which this package offers to `Instrumentations` and
+* `@btravstack/observability/otel` enables, traces at the ENGINE level — the
+* real SQL, the connection acquisition, the serialisation — all of it below
+* what a client-level wrapper can see. Emitting a span here as well would put two
 * spans on every query for strictly less information. What this wrapper keeps
 * is the pair Prisma's instrumentation does not do at all: a metric, and an
 * error line correlated with the ambient unit.
@@ -142,7 +143,7 @@ const prismaDatabase = (name) => ({ client }) => {
 		inject: { logger: Logger },
 		sync: ({ logger }) => () => loadPrismaInstrumentation(logger)
 	});
-	const chosen = Module(name)({
+	const database = Module(name)({
 		needs: [Env, Logger],
 		provides: [
 			config,
@@ -160,7 +161,7 @@ const prismaDatabase = (name) => ({ client }) => {
 			Instrumentations
 		]
 	});
-	return Object.assign(chosen, { port: DatabasePort });
+	return Object.assign(database, { port: DatabasePort });
 };
 //#endregion
 export { prismaDatabase };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@btravstack/prisma",
-  "version": "0.14.0",
+  "version": "0.15.0",
   "description": "The Prisma starter for @btravstack/core: DATABASE_URL through Config, the Postgres driver adapter, and a client whose pool is the application scope's",
   "keywords": [
     "database",
@@ -53,6 +53,9 @@
     "./package.json": "./package.json"
   },
   "devDependencies": {
+    "@btravstack/config": "0.15.0",
+    "@btravstack/core": "0.15.0",
+    "@btravstack/di": "0.15.0",
     "@btravstack/tsconfig": "0.4.0",
     "@prisma/adapter-pg": "7.10.0",
     "@prisma/client": "7.10.0",
@@ -63,19 +66,16 @@
     "tsdown": "0.23.0",
     "typescript": "7.0.2",
     "unthrown": "5.8.0",
-    "vitest": "4.1.11",
-    "@btravstack/config": "0.14.0",
-    "@btravstack/core": "0.14.0",
-    "@btravstack/di": "0.14.0"
+    "vitest": "4.1.11"
   },
   "peerDependencies": {
+    "@btravstack/config": "^0.15.0",
+    "@btravstack/core": "^0.15.0",
+    "@btravstack/di": "^0.15.0",
     "@prisma/adapter-pg": "^7.0.0",
     "@prisma/client": "^7.10.0",
     "@prisma/instrumentation": "^7.0.0",
-    "unthrown": "^5.0.0",
-    "@btravstack/config": "^0.14.0",
-    "@btravstack/core": "^0.14.0",
-    "@btravstack/di": "^0.14.0"
+    "unthrown": "^5.0.0"
   },
   "peerDependenciesMeta": {
     "@prisma/client": {
@@ -92,7 +92,6 @@
     "build": "tsdown src/index.ts src/rls.ts --format cjs,esm --dts --clean",
     "dev": "tsdown src/index.ts src/rls.ts --format cjs,esm --dts --watch",
     "test": "vitest run --coverage",
-    "test:types": "tsc -p tsconfig.test-d.json --noEmit",
     "typecheck": "tsc --noEmit && tsc --noEmit -p tsconfig.test-d.json"
   }
 }