@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
维护者通常 1 天内回复
还没有人认领这个 Issue。
- #418 来自 @kristof-siket —— 已关闭,未合并
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- nodejs, typescript
- 领域
- build-system, release
调研方向
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-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.
- 主要语言
- TypeScript
- 星标
- 6
- 派生
- 2
- 平均合并
- 1 天 9 小时
- 30 天内合并 PR
- 42
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
prisma/composer 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 90/100
维护者通常 1 天内回复
-
bug
难度 4/5 1-2 天 新手友好度 53/100
维护者通常 1 天内回复
-
enhancement
难度 4/5 3-5 天 新手友好度 42/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 52/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
thecodacus/understory#61 ·
-
bug
难度 2/5 1-3 小时 新手友好度 82/100
Termix-SSH/Plugin-Hosts-Config#14 · 1 条评论 ·
维护者通常 4 天内回复
-
ai-generated priority: p2 size: s type: bug
难度 2/5 1-3 小时 新手友好度 82/100
JonathanTSilva/jts-website#92 ·
维护者通常 1 天内回复
-
Toast announcer reads a doubled period when a toast's title ends in punctuation可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100
vercel-labs/ui#999 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
ehmpathy/rhachet-roles-ehmpathy#1443 ·
维护者通常 1 天内回复