What is the problem?
给中文新手的 build 失败排查流程：先区分 dev 和 build，再检查 TypeScript、lint、环境变量、静态生成、依赖版本、大小写路径和部署环境差异。
Quick solution
Treat this as a Vercel 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
- 保存完整日志。复制 `npm run build` 的完整输出，不要只保存最后一行。
- 确认本地复现。先在项目根目录运行 build，不要只看部署平台截图。
- 找失败阶段。看是 TypeScript、lint、静态生成、依赖安装、图片处理、路由生成，还是环境变量校验。
- 检查环境变量。确认 build 需要哪些变量，哪些可以为空，哪些必须由客户确认。
- 检查路径大小写。Windows 本地可能不敏感，Linux 部署环境可能敏感。
- 检查动态代码。静态生成时访问浏览器对象、读取不存在的数据、调用未授权接口，都可能失败。
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.