Upgrade to Next.js 16.3 + migrate to App Router + adopt Cache Components #4203
aurorascharffsite_lint.yml
on: pull_request
Lint on node 20.x and ubuntu-latest
1m 31s
Annotations
8 warnings
|
Lint on node 20.x and ubuntu-latest
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Lint on node 20.x and ubuntu-latest:
src/components/MDX/MDXComponents.tsx#L520
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 on node 20.x and ubuntu-latest:
src/components/MDX/MDXComponents.tsx#L380
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 on node 20.x and ubuntu-latest:
src/components/MDX/MDXComponents.tsx#L344
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 on node 20.x and ubuntu-latest:
src/components/Layout/HomeContent.js#L1645
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 on node 20.x and ubuntu-latest:
src/components/Layout/HomeContent.js#L1568
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 on node 20.x and ubuntu-latest:
src/components/Layout/HomeContent.js#L806
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 on node 20.x and ubuntu-latest:
src/components/Layout/HomeContent.js#L513
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
|