This repository has been archived by the owner on Dec 6, 2024. It is now read-only.
refac: refactor product module #73
EjembiEmmanuelfrontend.yml
on: pull_request
lint-and-build-frontend
44s
Annotations
5 warnings
|
lint-and-build-frontend:
frontend/src/app/producers/page.tsx#L101
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
|
|
lint-and-build-frontend:
frontend/src/components/ProductPreview.tsx#L75
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
|
|
lint-and-build-frontend:
frontend/src/components/ProductPreview.tsx#L83
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
|
|
lint-and-build-frontend:
frontend/src/components/Scan.tsx#L96
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
|
|
lint-and-build-frontend:
frontend/src/components/Scan.tsx#L198
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
|