@prisma/composer 0.32.0-dev.2 → 0.32.0-dev.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@prisma/composer",
3
- "version": "0.32.0-dev.2",
3
+ "version": "0.32.0-dev.3",
4
4
  "type": "module",
5
5
  "description": "Prisma Composer — build a Prisma App by composing Modules. Core authoring, deploy pipeline, and the service-rpc/http/node/nextjs authoring surfaces. The command family the `prisma` CLI mounts lives in @prisma/composer-cli.",
6
6
  "exports": {
@@ -40,16 +40,16 @@
40
40
  "@prisma/management-api-sdk": "^1.80.0"
41
41
  },
42
42
  "devDependencies": {
43
- "@internal/assemble": "0.32.0-dev.2",
44
- "@internal/cli": "0.32.0-dev.2",
45
- "@internal/core": "0.32.0-dev.2",
46
- "@internal/foundation": "0.32.0-dev.2",
47
- "@internal/http": "0.32.0-dev.2",
48
- "@internal/lowering": "0.32.0-dev.2",
49
- "@internal/nextjs": "0.32.0-dev.2",
50
- "@internal/node": "0.32.0-dev.2",
51
- "@internal/service-rpc": "0.32.0-dev.2",
52
- "@internal/tsdown-config": "0.32.0-dev.2",
43
+ "@internal/assemble": "0.32.0-dev.3",
44
+ "@internal/cli": "0.32.0-dev.3",
45
+ "@internal/core": "0.32.0-dev.3",
46
+ "@internal/foundation": "0.32.0-dev.3",
47
+ "@internal/http": "0.32.0-dev.3",
48
+ "@internal/lowering": "0.32.0-dev.3",
49
+ "@internal/nextjs": "0.32.0-dev.3",
50
+ "@internal/node": "0.32.0-dev.3",
51
+ "@internal/service-rpc": "0.32.0-dev.3",
52
+ "@internal/tsdown-config": "0.32.0-dev.3",
53
53
  "@types/node": "^26.0.1",
54
54
  "tsdown": "^0.22.7",
55
55
  "typescript": "^6.0.3"
@@ -2,7 +2,7 @@
2
2
  name: prisma-composer-core-concepts
3
3
  metadata:
4
4
  library: "@prisma/composer"
5
- library_version: "0.32.0-dev.2"
5
+ library_version: "0.32.0-dev.3"
6
6
  version: 2026.9.1
7
7
  description: >-
8
8
  Use when deploying or managing an app that uses Prisma Composer
@@ -287,16 +287,29 @@ Two kinds of Postgres dependency:
287
287
 
288
288
  1. **`rawPostgres()`**: the binding is `{ url }` and the app owns its client.
289
289
  2. **`postgres(...)`**: a Prisma-ORM-typed database. The binding is
290
- `{ url, client }` (ADR-0040): the raw connection URL plus the typed
291
- client Composer constructs from your data contract, lazily on first
292
- access, so queries go through `binding.client` and are compile-time
293
- checked. Both `postgres` and `dataContract` import from
290
+ `{ url, connection, client, clientWith }` (ADR-0040, ADR-0055): the raw
291
+ connection URL, the connection pool, the typed client Composer constructs
292
+ from your data contract lazily on first access, and `clientWith(options)`,
293
+ which builds a typed client with Prisma ORM runtime options. Queries go
294
+ through `binding.client` and are compile-time checked. Both `postgres` and `dataContract` import from
294
295
  `@prisma/composer-prisma-cloud/orm`, not the package root. One
295
296
  `dataContract`-wrapped value (emitted from `contract.prisma` by
296
297
  `prisma contract emit`) is referenced by both the dependency end
297
298
  (`deps: { db: postgres(catalogData) }`) and the resource end, which also
298
299
  names the `prisma.config.ts` path so the deploy's migration step can
299
300
  reload the emitted `contract.json` and find `migrations/`.
301
+ Client options never go on the dependency declaration. A contract that
302
+ uses an extension type (for example `pgvector.Vector(length: 1024)`)
303
+ needs the pack's runtime extension when the client is built:
304
+ `export const orm = db.clientWith({ extensions: [pgvectorRuntime] })`,
305
+ where `pgvectorRuntime` is the default export of
306
+ `@prisma/orm-extension-pgvector/runtime`; other runtime options, such as
307
+ `middleware`, go in the same object. Install the pack at exactly the
308
+ `@prisma/orm-postgres` version: the pack pins the ORM's shared packages
309
+ to its own version, so a mismatch installs two copies that silently
310
+ reject each other's values. Composer never looks extensions up itself;
311
+ with `binding.client` instead, the first access throws
312
+ "Contract requires extension pack(s) 'pgvector'".
300
313
 
301
314
  **Deploys are replay-only**: they apply the migrations committed under
302
315
  `migrations/` and never create schema themselves. Every schema change,