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

alert system component #49

alert system component

alert system component #49

Triggered via pull request November 25, 2024 14:58
@JemiiahJemiiah
synchronize #52
Jemiiah:fix-36
Status Failure
Total duration 37s
Artifacts

frontend.yml

on: pull_request
lint-and-build-frontend
28s
lint-and-build-frontend
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
lint-and-build-frontend
Process completed with exit code 1.
lint-and-build-frontend
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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#L33
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#L41
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