What is the problem?
给中文新手的 dependency conflict 依赖冲突排查流程：先保存报错和锁文件状态，再看包管理器、peer dependency、版本范围、Node 版本和验证命令，不要一上来强制安装。
Quick solution
Treat this as a Node.js errors tutorial issue. First confirm the environment, inputs, permissions, logs, and delivery boundary. Then use the linked deep guide for the full checklist before changing production code or promising a result.
Read the deep guideDetailed steps
- 保存原始报错。复制完整安装命令、报错片段、当前目录、Node 版本、包管理器版本。
- 确认包管理器。看项目里是 `package-lock.json`、`yarn.lock` 还是 `pnpm-lock.yaml`，不要混用。
- 看冲突对象。找到报错中互相冲突的包名、要求版本和当前安装版本。
- 看 `package.json`。确认冲突包是直接依赖、开发依赖，还是被其他包间接引入。
- 看 Node 版本。部分依赖要求特定 Node 范围，版本不符时改依赖未必有用。
- 小步尝试。先查版本关系和项目说明，再决定是调整版本、升级插件、降级主包，还是保留旧依赖。
Commands or code
The source article does not include a copyable command block. Do not invent commands here; follow the diagnostic steps in the deep guide and validate changes in the real project environment.
Risk notes
Confirm the real project environment, account permissions, platform rules, and output quality before delivery. Do not ship AI-generated changes without human review, and do not claim indexing, income, deployment success, or ranking improvements without measured evidence.