@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 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

  • #418 @kristof-siket による — マージされずにクローズ

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
45/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
nodejs, typescript

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.
主要言語
TypeScript
スター
6
フォーク
2
平均マージ
1日 9時間
マージ済み PR(30日)
42

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

prisma/composer のほかの issue

prisma/composer の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。