pnpm test can fail at random because the engine's test script rebuilds its dist while the CLI's tests import it

未关闭
#296 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
76/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
typescript

调研方向

Start with packages/cli-engine/package.json, tsdown.config.ts, and turbo.json, then run pnpm test repeatedly to reproduce the intermittent resolution failure. Confirm the CLI test task waits for the engine build and that the engine test run no longer cleans dist/ during parallel tests; pnpm test should complete reliably.

由索引模型根据 Issue 内容生成。

描述

packages/cli-engine/package.json's test script is pnpm run build && pnpm run typecheck && vitest run, and tsdown.config.ts has clean: true. Under the parallel pnpm test, the engine's test task can delete and rewrite dist/ while the CLI's tests are importing it, which fails with Failed to resolve entry for package "@prisma/cli-engine". In turbo.json, test depends only on ^build. Turbo cache hits hide it most of the time.

The fix the ledger proposed: make the CLI's test task depend on the engine's build, and stop the engine's test script from cleaning dist/ mid-run.

Recorded in the prisma-cli-v8 project ledger, which is being deleted at project close-out: https://github.com/prisma/prisma-cli/blob/4356b361adf7044bae59aa0bc70340eda89fdad6/.drive/projects/prisma-cli-v8/deferred.md#L400

🤖 Generated with Claude Code

主要语言
TypeScript
星标
25
派生
4
平均合并
18 小时 22 分钟
30 天内合并 PR
34

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

prisma/prisma-cli 的其他 Issue

查看 prisma/prisma-cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。