@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
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
- Área
- build-system, release
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-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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 6
- Forks
- 2
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 42
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de prisma/composer
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 4/5 1-2 días Aptitud para principiantes 53/100
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
prisma/composer#329 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de prisma/composer
Issues similares
-
dream report: normalizeMutation discards ok/status, consumers can only string-match the summaryAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
thecodacus/understory#61 ·
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Termix-SSH/Plugin-Hosts-Config#14 · 1 comentario ·
Los mantenedores suelen responder en 4 días
-
ai-generated priority: p2 size: s type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
JonathanTSilva/jts-website#92 ·
Los mantenedores suelen responder en 1 día
-
Toast announcer reads a doubled period when a toast's title ends in punctuationPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
vercel-labs/ui#999 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
ehmpathy/rhachet-roles-ehmpathy#1443 ·
Los mantenedores suelen responder en 1 día