Next.js アプリが Amplify ホスティングでデプロイ失敗

以下は Amplify デプロイ失敗ログ：

59 2024-10-10T14:17:02.799Z [INFO]: ✓ Compiled successfully
60 2024-10-10T14:17:02.805Z [INFO]: Linting and checking validity of types ...
61 2024-10-10T14:17:05.334Z [WARNING]: Failed to compile.
62 2024-10-10T14:17:05.335Z [WARNING]: ./app/books/[bookId]/edit/page.tsx
63 53:43 Error: Unexpected any. Specify a different type. @typescript-eslint/no-explicit-any
64 175:13 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
65 ./app/books/[bookId]/page.tsx
66 266:17 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
67 ./app/create/page.tsx
68 175:13 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
69 ./app/preview/page.tsx
70 46:15 Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
71 info - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
72 2024-10-10T14:17:05.351Z [ERROR]: !!! Build failed

Error: Unexpected any. Specify a different type. @typescript-eslint/no-explicit-any

とあるように、

any

だと失敗するようだ。 型を明確に記述したところデプロイ成功した。