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

Merge pull request #79 from nexlabsweb3/fix_navbar #90

Merge pull request #79 from nexlabsweb3/fix_navbar

Merge pull request #79 from nexlabsweb3/fix_navbar #90

Triggered via push November 28, 2024 11:50
Status Success
Total duration 54s
Artifacts

frontend.yml

on: push
lint-and-build-frontend
44s
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#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