Skip to content

feat(image, react-image): add LoadClient, update load can return image, export all public apis of @fepack/image in @fepack/react-image #180

feat(image, react-image): add LoadClient, update load can return image, export all public apis of @fepack/image in @fepack/react-image

feat(image, react-image): add LoadClient, update load can return image, export all public apis of @fepack/image in @fepack/react-image #180

Triggered via pull request September 24, 2023 19:08
Status Cancelled
Total duration 1m 27s
Artifacts

ci.yml

on: pull_request
Matrix: Check quality
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
Check quality (test)
Canceling since a higher priority waiting request for 'CI-refs/pull/44/merge' exists
Check quality (test)
The operation was canceled.
Check quality (lint): websites/demo-react-image-next/src/app/load/page.tsx#L15
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
Check quality (lint): websites/demo-react-image-next/src/app/page.tsx#L15
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
Check quality (lint): websites/demo-react-image-next/src/app/page.tsx#L22
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