react 19: the Dependabot halves cannot resolve alone, so the bump needs one combined PR
维护者通常 4 天内回复
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 70/100
- Issue 类型
- 重构
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, react, typescript
- 领域
- build-system, frontend
调研方向
先从 website/package.json 开始,然后检查 website/package-lock.json 和 .github/workflows/deploy.yml;两个失败的 Dependabot PR 是 #401/#402,它们解释了为什么未合并的 lockfile 会破坏 Pages 部署。在 website 中升级 react、react-dom 和 @types/react-dom,用 npm install 重新生成 lockfile,然后用 npm ci 和 npm run build 进行验证。当合并后的 PR 能干净地安装且构建通过时即完成;过时的 yarn packageManager/resolutions 清理留到单独的改动中处理。
由索引模型根据 Issue 内容生成。
描述
Dependabot opened the react 19 major as two PRs, and neither can pass on its own:
- #401 bumps
react18.3.1 to 19.3.1 - #402 bumps
react-domand@types/react-domto 19.3.1 / 19.3.0
Each half breaks the other's peer requirement, so both fail npm ci with ERESOLVE:
#402: Found: [email protected]
Could not resolve dependency: peer react@^19.3.1 from [email protected]
#401: Found: [email protected]
Could not resolve dependency: peer react-dom@^18.3.1 from [email protected]
Merging them one after the other does not fix it either. deploy.yml runs on every push to main, so between the two merges the tracked lockfile does not resolve, the build job fails, and the Pages deploy is skipped. Any PR opened in that window inherits the same broken lockfile.
Proposed fix
One PR that takes the peer set together, with a regenerated lockfile:
reactandreact-domto^19.3.1@types/react-domto^19.3.0(19.3.1 does not exist)
Verified locally against main at 973801b:
npm installwith the bumped versions: 1409 packages, no ERESOLVEnpm ciagainst the regeneratedwebsite/package-lock.json: exit 0npm run build: SUCCESS, static files generated
@docusaurus/core 3.10.2 declares react ^18.0.0 || ^19.0.0, so 19 is inside the supported range. The @slorber/react-helmet-async alias it depends on prints a peer warning capped at react 18, and the install still exits 0.
Related, separate
website/package.json still carries packageManager: [email protected] and a resolutions block pinning react and react-dom to ^18.3.1, both stale since the repo standardised on npm. A yarn install would put react 18 back. npm ignores both, so this does not block the bump, but it should be cleaned up in its own change.
Also worth considering: a groups entry in .github/dependabot.yml covering the peer set, so the next react major arrives as one PR instead of two unresolvable halves.
- 主要语言
- TypeScript
- 星标
- 13
- 派生
- 24
- 平均合并
- 2 天 3 小时
- 30 天内合并 PR
- 16
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
IntersectMBO/developer-experience 的其他 Issue
-
Rename the q4-2025 sesion-notes folder to session-notes, and keep its URL working可能已有人在做 @IanoNjuguna 今天认领。 未关闭documentation Low Priority
难度 2/5 1-3 小时 新手友好度 62/100
IntersectMBO/developer-experience#406 ·
维护者通常 4 天内回复
-
Document colour roles in the brand baseline, and resolve the gradient and alpha restrictions it contradicts可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭documentation
难度 2/5 1-3 小时 新手友好度 72/100
IntersectMBO/developer-experience#376 ·
维护者通常 4 天内回复
-
documentation pinned
难度 2/5 1-3 小时 新手友好度 90/100
IntersectMBO/developer-experience#363 · 1 条评论 ·
维护者通常 4 天内回复
-
documentation pinned
难度 2/5 1-3 小时 新手友好度 88/100
IntersectMBO/developer-experience#362 · 1 条评论 ·
维护者通常 4 天内回复
-
documentation pinned
难度 2/5 1-3 小时 新手友好度 90/100
IntersectMBO/developer-experience#360 · 1 条评论 ·
维护者通常 4 天内回复
查看 IntersectMBO/developer-experience 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 82/100
维护者通常 1 天内回复
-
Update project links after the repository renames可能已有人在做 @JonathanTSilva 今天认领。 未关闭ai-generated priority: p2 size: xs type: bug
难度 2/5 1-3 小时 新手友好度 85/100
JonathanTSilva/jts-website#119 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 74/100
promplate/code-review#158 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
[Docs] CONTRIBUTING points the Backend Remake milestone at a branch that does not exist可能已有人在做 @franpts2 今天认领。 未关闭docs
难度 1/5 1 小时以内 新手友好度 90/100
维护者通常 3 天内回复