@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

Abierto
#413 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

  • #418 de @kristof-siket — cerrado sin fusionar

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
nodejs, typescript

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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-postgres 8.0.0-rc.22 (latest, published 2026-10-30), @prisma/composer-prisma-cloud 0.36.0 (latest)
Additional context
  • The prisma CLI side of the version skew is prisma/prisma-cli#382; its toolchain bump is merged in prisma/prisma-cli#381 but unreleased.
  • Related: @prisma/composer lists @effect/[email protected] as a runtime dependency, which peers vitest >=5 <6. npm nests a second [email protected] under @prisma/composer in 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.
Lenguaje dominante
TypeScript
Estrellas
6
Forks
2
Merge medio
1 d 9 h
PR fusionados (30 d)
42

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de prisma/composer

Todos los issues de prisma/composer

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.