@prisma/composer 0.17.0-dev.5 → 0.17.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.17.0-dev.5",
3
+ "version": "0.17.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": {
@@ -29,6 +29,7 @@
29
29
  "dependencies": {
30
30
  "@effect/sql-d1": "4.0.0-rc.112",
31
31
  "@effect/sql-sqlite-do": "4.0.0-rc.112",
32
+ "@effect/vitest": "4.0.0-rc.112",
32
33
  "@standard-schema/spec": "^1.1.0",
33
34
  "alchemy": "2.0.0-beta.74",
34
35
  "arktype": "^2.2.3",
@@ -39,16 +40,15 @@
39
40
  "@prisma/management-api-sdk": "^1.60.0"
40
41
  },
41
42
  "devDependencies": {
42
- "@effect/vitest": "4.0.0-rc.112",
43
- "@internal/assemble": "0.17.0-dev.5",
44
- "@internal/cli": "0.17.0-dev.5",
45
- "@internal/core": "0.17.0-dev.5",
46
- "@internal/foundation": "0.17.0-dev.5",
47
- "@internal/lowering": "0.17.0-dev.5",
48
- "@internal/nextjs": "0.17.0-dev.5",
49
- "@internal/node": "0.17.0-dev.5",
50
- "@internal/service-rpc": "0.17.0-dev.5",
51
- "@internal/tsdown-config": "0.17.0-dev.5",
43
+ "@internal/assemble": "0.17.0-dev.7",
44
+ "@internal/cli": "0.17.0-dev.7",
45
+ "@internal/core": "0.17.0-dev.7",
46
+ "@internal/foundation": "0.17.0-dev.7",
47
+ "@internal/lowering": "0.17.0-dev.7",
48
+ "@internal/nextjs": "0.17.0-dev.7",
49
+ "@internal/node": "0.17.0-dev.7",
50
+ "@internal/service-rpc": "0.17.0-dev.7",
51
+ "@internal/tsdown-config": "0.17.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.17.0-dev.5"
5
+ library_version: "0.17.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
@@ -431,13 +431,13 @@ today the blocks above plus your own Modules are the whole set, so verify a
431
431
 
432
432
  1. **Every `prisma-composer` command halts at start-up on an `effect`
433
433
  version conflict** (`Dependency conflict: alchemy resolves effect@...`).
434
- Another dependency floated a newer `effect` and the package manager
435
- hoisted it over Composer's pin. Pin the whole `effect` constellation in
436
- the app's `package.json` `overrides` (yarn: `resolutions`; pnpm:
437
- `pnpm.overrides`): `effect` plus `@effect/sql-d1`, `@effect/sql-pg`,
438
- `@effect/vitest`, and `@effect/platform-bun`/`-node`/`-node-shared`, all
439
- at Composer's exact pin, then reinstall. The repo's examples carry the
440
- block.
434
+ The app, or one of its dependencies, pins a different `effect` and the
435
+ package manager hoisted it over Composer's pin. Match the app's own
436
+ `effect` to `@prisma/composer`'s exact pin, or force it with
437
+ `"overrides": { "effect": "<pin>" }` in the app's `package.json` (yarn:
438
+ `resolutions`; pnpm: `pnpm.overrides`), then reinstall. A plain Composer
439
+ app never hits this: the public packages pin every `effect`-family
440
+ package alchemy would float.
441
441
  2. **A deployed `/rpc/<method>` returns `401` to anything but a wired
442
442
  peer.** Not a broken deploy; see Contracts above.
443
443
  3. **Scale-to-zero closes idle database connections.** A persistent client