Skip to content
This repository has been archived by the owner on Dec 6, 2024. It is now read-only.

Merge pull request #85 from Joy-Adah/manufacturer_account_creation #111

Merge pull request #85 from Joy-Adah/manufacturer_account_creation

Merge pull request #85 from Joy-Adah/manufacturer_account_creation #111

Triggered via push December 1, 2024 09:26
Status Success
Total duration 58s
Artifacts

frontend.yml

on: push
lint-and-build-frontend
49s
lint-and-build-frontend
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
lint-and-build-frontend: frontend/src/components/ProductPreview.tsx#L76
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#L84
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#L112
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#L214
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