@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
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
- #418 di @kristof-siket — chiusa senza merge
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 45/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- nodejs, typescript
- Ambito
- build-system, release
Direzione di ricerca
The conflict is in the @prisma/composer-prisma-cloud package manifest: the exact peerDependencies pin on @prisma/orm-postgres and the @prisma/orm-toolchain dependency, both at 8.0.0-rc.20. Run the reproduction from the issue body to confirm the ERESOLVE failure with rc.22. Done means the install resolves against the current ORM release, which needs a maintainer decision on the peer range or on bumping the pin during release.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Package and version
@prisma/[email protected] (current latest), with @prisma/[email protected].
What happened?
@prisma/composer-prisma-cloud declares an exact peer dependency on @prisma/[email protected] and depends on @prisma/[email protected]. 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/[email protected]
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/[email protected]
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/[email protected]. 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 [email protected] + @prisma/[email protected] + @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/[email protected] @prisma/[email protected] @prisma/[email protected]
# ERESOLVE, output above
npm view @prisma/[email protected] 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/[email protected] 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/prisma-cli#382; its toolchain bump is merged in prisma/prisma-cli#381 but unreleased. - Related:
@prisma/composerlists@effect/[email protected]as a runtime dependency, which peersvitest >=5 <6. npm nests a second[email protected]under@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 (QwikDev/qwik#9357 and QwikDev/qwik#9358). The Compute deployment instructions were left out of the Qwik docs because of these pins.
- Lingua principale
- TypeScript
- Stelle
- 6
- Fork
- 2
- Merge medio
- 1g 9h
- PR unite (30g)
- 42
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di prisma/composer
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 4/5 1-2 giorni Idoneità per principianti 53/100
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 4/5 3-5 giorni Idoneità per principianti 42/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 52/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
prisma/composer#329 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di prisma/composer
Issue simili
-
dream report: normalizeMutation discards ok/status, consumers can only string-match the summaryAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
thecodacus/understory#61 ·
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
Termix-SSH/Plugin-Hosts-Config#14 · 1 commento ·
I maintainer di solito rispondono entro 4 giorni
-
ai-generated priority: p2 size: s type: bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
JonathanTSilva/jts-website#92 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
vercel-labs/ui#999 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
ehmpathy/rhachet-roles-ehmpathy#1443 ·
I maintainer di solito rispondono entro 1 giorno