@prisma/composer 0.20.0-dev.6 → 0.20.0-dev.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prisma/composer",
-  "version": "0.20.0-dev.6",
+  "version": "0.20.0-dev.8",
   "type": "module",
   "description": "Prisma Composer — build a Prisma App by composing Modules. Core authoring, deploy pipeline, and the service-rpc/node/nextjs authoring surfaces. The `prisma-composer` CLI lives in @prisma/composer-cli.",
   "exports": {
@@ -40,15 +40,15 @@
     "@prisma/management-api-sdk": "^1.60.0"
   },
   "devDependencies": {
-    "@internal/assemble": "0.20.0-dev.6",
-    "@internal/cli": "0.20.0-dev.6",
-    "@internal/core": "0.20.0-dev.6",
-    "@internal/foundation": "0.20.0-dev.6",
-    "@internal/lowering": "0.20.0-dev.6",
-    "@internal/nextjs": "0.20.0-dev.6",
-    "@internal/node": "0.20.0-dev.6",
-    "@internal/service-rpc": "0.20.0-dev.6",
-    "@internal/tsdown-config": "0.20.0-dev.6",
+    "@internal/assemble": "0.20.0-dev.8",
+    "@internal/cli": "0.20.0-dev.8",
+    "@internal/core": "0.20.0-dev.8",
+    "@internal/foundation": "0.20.0-dev.8",
+    "@internal/lowering": "0.20.0-dev.8",
+    "@internal/nextjs": "0.20.0-dev.8",
+    "@internal/node": "0.20.0-dev.8",
+    "@internal/service-rpc": "0.20.0-dev.8",
+    "@internal/tsdown-config": "0.20.0-dev.8",
     "@types/node": "^26.0.1",
     "tsdown": "^0.22.7",
     "typescript": "^6.0.3"

package/skills/prisma-composer-core-concepts/SKILL.md

@@ -2,7 +2,7 @@
 name: prisma-composer-core-concepts
 metadata:
   library: "@prisma/composer"
-  library_version: "0.20.0-dev.6"
+  library_version: "0.20.0-dev.8"
   version: 2026.9.1
 description: >-
   Use when deploying or managing an app that uses Prisma Composer
@@ -369,12 +369,13 @@ that surprise:
    service it calls.
 5. Windows isn't supported yet.
 
-Local Postgres needs `@prisma/dev` in the devDependencies of the project where
-Composer runs (the root package in a monorepo). Prisma 8 does not ship it.
-Composer resolves the app's copy first, then checks relative to the exported
-`prisma/package.json` for installations that supply it there. If neither resolves,
-add `@prisma/dev`, not another copy of `prisma`; leave database bindings unchanged.
-Cloud deployment and local apps without Postgres do not need this runtime.
+Local Postgres runs on `@prisma/dev`, which `@prisma/composer-prisma-cloud`
+declares as its own dependency (`^0.25.2`) and resolves from its own package.
+Nothing needs adding to the app, and an app's own `@prisma/dev` (for example the
+`^0.20.0` alchemy pulls in, which crashes on any Postgres message over 64 KiB) is
+ignored. If the emulator reports that `@prisma/dev` did not resolve, the install
+is broken: reinstall dependencies rather than adding `@prisma/dev` or `prisma`.
+Cloud deployment and local apps without Postgres never load this runtime.
 
 ## Testing is an environment seam
 
@@ -451,9 +452,10 @@ today the blocks above plus your own Modules are the whole set, so verify a
    crashes into a 502 restart loop unless the pool is small and
    reconnect-friendly (`new SQL({ url, max: 1, idleTimeout: 10 })` for Bun)
    and the process logs `uncaughtException`/`unhandledRejection` instead of
-   dying. Under `dev` watch-restarts against the local emulator, add
-   `prepare: false` as well: restarted processes collide on
-   prepared-statement names in the emulator's shared session.
+   dying. Under `dev`, add `prepare: false` as well: the local Postgres
+   is one session shared by every connection and it outlives your
+   processes, so a restarted process collides on prepared-statement
+   names (42P05) and crash-loops.
 4. **Cold starts reset service-to-service connections.** A call into a
    scaled-to-zero service can get `ECONNRESET`; retry it.
 5. **Bind `0.0.0.0`, not loopback.** The platform routes external HTTP to