Repository navigation
@prisma/composer-prisma-cloud 0.36.0 peer-pins @prisma/orm-postgres 8.0.0-rc.20, so it cannot be installed next to the current ORM rc.22 without --legacy-peer-deps #413
Description
Package and version
@prisma/composer-prisma-cloud@0.36.0 (current latest), with @prisma/composer@0.36.0.
What happened?
@prisma/composer-prisma-cloud declares an exact peer dependency on @prisma/orm-postgres@8.0.0-rc.20 and depends on @prisma/orm-toolchain@8.0.0-rc.20. The current ORM latest is 8.0.0-rc.22, so a project on the current ORM cannot install the Compute provider with npm:
npm error ERESOLVE unable to resolve dependency tree
npm error Found: @prisma/orm-postgres@8.0.0-rc.22
npm error @prisma/orm-postgres@"8.0.0-rc.22" from the root project
npm error Could not resolve dependency:
npm error peer @prisma/orm-postgres@"8.0.0-rc.20" from @prisma/composer-prisma-cloud@0.36.0
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
The only ways through are --legacy-peer-deps, or pinning the whole app back to @prisma/orm-postgres@8.0.0-rc.20. Both put a different @prisma/orm-toolchain in the tree from the one the prisma CLI bundles, which is the same mismatch that breaks contract emit (prisma/prisma-cli#382). When I deployed a Qwik app to Compute on 2026-11-02, the working set was prisma@8.0.0-rc.28 + @prisma/orm-postgres@8.0.0-rc.20 + @prisma/composer*@0.35.0, installed with --legacy-peer-deps. That is not something a getting-started path can ask for.
What did you expect to happen?
Installing @prisma/composer and @prisma/composer-prisma-cloud next to the current @prisma/orm-postgres@latest resolves. Either the peer range tracks the ORM's release line (for example >=8.0.0-rc.20 <9, or the range the provider is actually tested against), or the release process bumps the pin in the same release as the ORM.
Minimal reproduction
mkdir repro && cd repro && npm init -y
npm install --package-lock-only @prisma/orm-postgres@8.0.0-rc.22 @prisma/composer@0.36.0 @prisma/composer-prisma-cloud@0.36.0
# ERESOLVE, output above
npm view @prisma/composer-prisma-cloud@0.36.0 peerDependencies dependencies
# peerDependencies: { "@prisma/orm-postgres": "8.0.0-rc.20" }
# dependencies include "@prisma/orm-toolchain": "8.0.0-rc.20"The same command with @prisma/orm-postgres@8.0.0-rc.20 resolves.
Environment
- npm 11.6.2, Node 24.11.1, macOS 15.6
@prisma/orm-postgres8.0.0-rc.22 (latest, published 2026-10-30),@prisma/composer-prisma-cloud0.36.0 (latest)
Additional context
- The
prismaCLI side of the version skew is prisma 8.0.0-rc.29 cannot emit with @prisma/orm-postgres 8.0.0-rc.22 (bundles orm-toolchain rc.21): fresh orm init fails, please release #381 prisma-cli#382; its toolchain bump is merged in Follow the products' released versions: @prisma/orm-toolchain 8.0.0-rc.21 -> 8.0.0-rc.22 prisma-cli#381 but unreleased. - Related:
@prisma/composerlists@effect/vitest@4.0.3as a runtime dependency, which peersvitest >=5 <6. npm nests a secondvitest@5.0.5under@prisma/composerin every app that installs it. It did not fail resolution in the reproduction above, so I am only noting it here. - Where I hit it: validating a Prisma ORM 8 setup for Qwik (docs(prisma): update the Prisma guide to Prisma ORM 8 and fix dead links QwikDev/qwik#9357 and feat(starters): move the qwik add prisma starter to Prisma ORM 8 with PostgreSQL QwikDev/qwik#9358). The Compute deployment instructions were left out of the Qwik docs because of these pins.
Activity