生产中奇怪的 next.js 错误：ENOENT：没有这样的文件或目录（图像缓存）

Question

我在 AWS EC2 上部署 next.js 时遇到问题。我npm run build然后npm run start，它工作得很好。此时，正如预期的那样，缓存中没有 webp 图像。然后我从浏览器加载网页，它工作正常。然而，当我有时加载页面时，它似乎随机崩溃。我收到上面的错误。似乎 webp 图像在某个时刻被从缓存中删除，并导致错误？有什么建议吗？

完整的错误是：

Error: ENOENT: no such file or directory, open '/home/ec2-user/prowash/pro-wash-site/.next/cache/images/7P-NdCEO6XWRTvqPItIV6CN1db-7IkBJw9kp3M5VafQ=/0.1647390677641.UEF7UxgKHha+us8b5ahYFWZH70qZHTAu2uyVPlYT7Hs=.webp'
Emitted 'error' event on ReadStream instance at:
    at emitErrorNT (node:internal/streams/destroy:164:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/home/ec2-user/prowash/pro-wash-site/.next/cache/images/7P-NdCEO6XWRTvqPItIV6CN1db-7IkBJw9kp3M5VafQ=/0.1647390677641.UEF7UxgKHha+us8b5ahYFWZH70qZHTAu2uyVPlYT7Hs=.webp'
}

Answer 1

也许使用构建脚本来设置权限，然后实施下一个构建。

通过此 文章：

1. 一个 Build.sh 脚本，在部署之前设置权限

#!/bin/bash

# Exit immediately if a command exits with a non-zero status
set -e


# building the Next.js application
npm run next:build

# creating the build/cache/images folder and give it
# the read/write permissions
mkdir -p .next/cache/images
chmod -R 666 .next/cache/images

2. 添加到 package.json 以确保它在 npm run 上运行构建

"scripts": {
  "build": "./build.sh"
}