NextJS部署AWS Amplify构建失败：缺失必要依赖文件amplify.sh

• 我们的NextJS项目部署在AWS Amplify上，此前构建部署完全正常，近期未修改任何代码，但构建阶段突然失败
• 核心报错：CustomerError: Required dependency file not found: /codebuild/output/src1250669152/src/tsv-webapp/amplify.sh
• 错误发生在构建缓存阶段完成之后，怀疑是AWS Amplify环境无法定位amplify.sh文件

构建日志详情：

2023-08-04T04:25:20.021Z [INFO]: # Completed phase: build
2023-08-04T04:25:20.023Z [INFO]: ## Build completed successfully
2023-08-04T04:25:20.101Z [INFO]: # Starting caching...
2023-08-04T04:25:20.110Z [INFO]: # Creating cache artifact...
2023-08-04T04:25:29.417Z [INFO]: # Created cache artifact
2023-08-04T04:25:29.502Z [INFO]: # Uploading cache artifact...
2023-08-04T04:25:34.357Z [INFO]: # Uploaded cache artifact
2023-08-04T04:25:34.448Z [INFO]: # Caching completed
2023-08-04T04:25:34.452Z [INFO]: Setting NEXT_PRIVATE_STANDALONE=true to produce .next/standalone directory
2023-08-04T04:25:34.455Z [INFO]: # No custom headers found.
2023-08-04T04:25:37.928Z [ERROR]: !!! CustomerError: Required dependency file not found: /codebuild/output/src1250669152/src/tsv-webapp/amplify.sh
2023-08-04T04:25:37.985Z [INFO]: # Starting environment caching...
2023-08-04T04:25:37.985Z [INFO]: # Environment caching completed
Terminating logging...

已知情况与修复建议 #

• 该问题并非个例，已有多个用户反馈类似情况，初步判定是AWS Amplify近期环境更新引发的兼容性问题，和用户代码无关
• 可尝试以下临时修复方案：
  • 强制清理构建缓存后重新部署：在Amplify控制台的构建页面选择「重新部署此版本」并勾选「清除缓存」
  • 若项目根目录无amplify.sh文件，手动创建一个空的amplify.sh文件后重新构建（部分用户验证此方法有效）
  • 关注官方相关问题进展，等待AWS推送正式修复补丁

内容的提问来源于stack exchange，提问作者Udantha