set single react types resolution #13822
Annotations
11 warnings
|
Lints:
frontends/main/src/app-pages/HomePage/TestimonialsSection.tsx#L262
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
|
Lints:
frontends/main/src/app-pages/ProgramLetterPage/[id]/view/ProgramLetterPage.tsx#L125
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
|
Lints:
frontends/main/src/app-pages/ProgramLetterPage/[id]/view/ProgramLetterPage.tsx#L142
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
|
Lints:
frontends/main/src/app-pages/ProgramLetterPage/[id]/view/ProgramLetterPage.tsx#L162
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
|
|
Lints:
frontends/main/src/page-components/TestimonialDisplay/AttestantBlock.tsx#L142
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
|
Lints:
frontends/ol-components/src/components/Banner/Banner.stories.tsx#L46
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
|
Lints:
frontends/ol-components/src/components/Banner/Banner.stories.tsx#L63
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
|
Lints:
frontends/ol-components/src/components/Logo/Logo.tsx#L93
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
|
Upload coverage to CodeCov
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/e28ff129e5465c2c0dcc6f003fc735cb6ae0c673/dist/codecov' failed with exit code 1
|
Loading