Migrate docs site to App Router on Next canary #3848
feedthejimsite_lint.yml
on: pull_request
Lint on node 20.x and ubuntu-latest
1m 7s
Annotations
7 warnings
|
Lint on node 20.x and ubuntu-latest:
src/components/MDX/MDXComponents.tsx#L390
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint on node 20.x and ubuntu-latest:
src/components/MDX/MDXComponents.tsx#L341
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint on node 20.x and ubuntu-latest:
src/components/MDX/MDXComponents.tsx#L307
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint on node 20.x and ubuntu-latest:
src/components/Layout/HomeContent.js#L1644
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint on node 20.x and ubuntu-latest:
src/components/Layout/HomeContent.js#L1567
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint on node 20.x and ubuntu-latest:
src/components/Layout/HomeContent.js#L805
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint on node 20.x and ubuntu-latest:
src/components/Layout/HomeContent.js#L512
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|