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

Merge pull request #86 from nexlabsweb3/fix_navbar #108

Merge pull request #86 from nexlabsweb3/fix_navbar

Merge pull request #86 from nexlabsweb3/fix_navbar #108

Triggered via push November 30, 2024 14:12
Status Success
Total duration 1m 3s
Artifacts

frontend.yml

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