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

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.20.0-dev.6",
3
+ "version": "0.20.0-dev.7",
4
4
  "type": "module",
5
5
  "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.",
6
6
  "exports": {
@@ -40,15 +40,15 @@
40
40
  "@prisma/management-api-sdk": "^1.60.0"
41
41
  },
42
42
  "devDependencies": {
43
- "@internal/assemble": "0.20.0-dev.6",
44
- "@internal/cli": "0.20.0-dev.6",
45
- "@internal/core": "0.20.0-dev.6",
46
- "@internal/foundation": "0.20.0-dev.6",
47
- "@internal/lowering": "0.20.0-dev.6",
48
- "@internal/nextjs": "0.20.0-dev.6",
49
- "@internal/node": "0.20.0-dev.6",
50
- "@internal/service-rpc": "0.20.0-dev.6",
51
- "@internal/tsdown-config": "0.20.0-dev.6",
43
+ "@internal/assemble": "0.20.0-dev.7",
44
+ "@internal/cli": "0.20.0-dev.7",
45
+ "@internal/core": "0.20.0-dev.7",
46
+ "@internal/foundation": "0.20.0-dev.7",
47
+ "@internal/lowering": "0.20.0-dev.7",
48
+ "@internal/nextjs": "0.20.0-dev.7",
49
+ "@internal/node": "0.20.0-dev.7",
50
+ "@internal/service-rpc": "0.20.0-dev.7",
51
+ "@internal/tsdown-config": "0.20.0-dev.7",
52
52
  "@types/node": "^26.0.1",
53
53
  "tsdown": "^0.22.7",
54
54
  "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.20.0-dev.6"
5
+ library_version: "0.20.0-dev.7"
6
6
  version: 2026.9.1
7
7
  description: >-
8
8
  Use when deploying or managing an app that uses Prisma Composer
@@ -451,9 +451,10 @@ today the blocks above plus your own Modules are the whole set, so verify a
451
451
  crashes into a 502 restart loop unless the pool is small and
452
452
  reconnect-friendly (`new SQL({ url, max: 1, idleTimeout: 10 })` for Bun)
453
453
  and the process logs `uncaughtException`/`unhandledRejection` instead of
454
- dying. Under `dev` watch-restarts against the local emulator, add
455
- `prepare: false` as well: restarted processes collide on
456
- prepared-statement names in the emulator's shared session.
454
+ dying. Under `dev`, add `prepare: false` as well: the local Postgres
455
+ is one session shared by every connection and it outlives your
456
+ processes, so a restarted process collides on prepared-statement
457
+ names (42P05) and crash-loops.
457
458
  4. **Cold starts reset service-to-service connections.** A call into a
458
459
  scaled-to-zero service can get `ECONNRESET`; retry it.
459
460
  5. **Bind `0.0.0.0`, not loopback.** The platform routes external HTTP to