fix(react-image): change Load to return loaded HTMLImageElement #234
manudeliAnnotations
7 errors and 3 warnings
|
Check quality (test)
Process completed with exit code 1.
|
|
Check quality (lint:pub)
The job was canceled because "test" failed.
|
|
Check quality (lint:pub)
The operation was canceled.
|
|
Check quality (type:check)
The job was canceled because "test" failed.
|
|
Check quality (type:check)
The operation was canceled.
|
|
Check quality (lint)
The job was canceled because "test" failed.
|
|
Check quality (lint)
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#L18
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#L25
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
|