Installing `prisma` hangs npm: composer-cli pins `effect@4.0.0-rc.112`, but alchemy pulls in newer `@effect/*` packages that require a newer `effect`

Package and version

@prisma/composer-cli@0.17.0 (also seen with 0.15.0, 0.16.0 and 0.17.0-dev.5), installed transitively by prisma@8.0.0-rc.11, rc.12 and rc.13.

What happened?

Installing the prisma CLI never completes. npm prints ERESOLVE overriding peer dependency for @effect/*@4.0.0-rc.114 packages in a loop and never exits, even in an empty project.

The relevant part of the tree:

prisma@8.0.0-rc.13
└─ @prisma/composer-cli@0.17.0
   ├─ effect                  4.0.0-rc.112              (exact pin)
   └─ alchemy@2.0.0-beta.74
      ├─ @effect/sql-d1        ">=4.0.0-rc.110 || >=4.0.0"
      ├─ @effect/sql-sqlite-do ">=4.0.0-rc.110 || >=4.0.0"
      └─ @effect/vitest        ">=4.0.0-rc.110 || >=4.0.0"

What did you expect to happen?

Installing the prisma CLI resolves a consistent dependency tree, whichever @effect/* versions were published most recently.

Minimal reproduction

Following the Prisma 8 "add to an existing project" docs in a fresh folder:

1. npm init -y
2. npm install --save-dev tsx typescript (completes normally)
3. npx prisma@latest orm init --target postgres, then accept installing prisma@8.0.0-rc.13. It never completes, and loops on:

npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @effect/sql-d1@4.0.0-rc.114
npm warn Found: peer effect@"^4.0.0-rc.114" from the root project
npm warn Could not resolve dependency:
npm warn peer effect@"^4.0.0-rc.114" from the root project

The first warning is for @effect/vitest@4.0.0-rc.114; after that it repeats for @effect/sql-d1.

Environment

• Node: 26.8.1
• OS: Windows 11 (10.0.26200)
• Package manager: npm 11.19.1

Additional context

Adding these root overrides makes the dry run resolve cleanly in about 70 seconds:

"overrides": {
  "@effect/sql-d1": "4.0.0-rc.112",
  "@effect/sql-sqlite-do": "4.0.0-rc.112",
  "@effect/vitest": "4.0.0-rc.112"
}

Start by reproducing the install from the listed Prisma command and inspect the package manifests for @prisma/composer-cli, alchemy, effect, and the @effect/* packages. Trace the incompatible version and peer-dependency declarations, then verify that a fresh npm install completes without the repeated ERESOLVE warnings using the reported versions.