Migrate docs site to App Router on Next canary #3849
feedthejimsite_lint.yml
on: pull_request
Lint on node 20.x and ubuntu-latest
1m 33s
Annotations
10 errors and 7 warnings
|
Lint on node 20.x and ubuntu-latest:
src/components/MDX/Sandpack/generatedHooksLint.ts#L2124
'i' is defined but never used
|
|
Lint on node 20.x and ubuntu-latest:
src/components/MDX/Sandpack/generatedHooksLint.ts#L717
't' is defined but never used
|
|
Lint on node 20.x and ubuntu-latest:
src/components/MDX/Sandpack/generatedHooksLint.ts#L681
'n' is defined but never used
|
|
Lint on node 20.x and ubuntu-latest:
src/components/MDX/Sandpack/generatedHooksLint.ts#L446
'n' is defined but never used
|
|
Lint on node 20.x and ubuntu-latest:
src/components/MDX/Sandpack/generatedHooksLint.ts#L326
'e' is defined but never used
|
|
Lint on node 20.x and ubuntu-latest:
src/components/MDX/Sandpack/generatedHooksLint.ts#L218
'i' is defined but never used
|
|
Lint on node 20.x and ubuntu-latest:
src/components/MDX/Sandpack/generatedHooksLint.ts#L217
'r' is defined but never used
|
|
Lint on node 20.x and ubuntu-latest:
src/components/MDX/Sandpack/generatedHooksLint.ts#L213
'e' is defined but never used
|
|
Lint on node 20.x and ubuntu-latest:
src/components/MDX/Sandpack/generatedHooksLint.ts#L210
'e' is defined but never used
|
|
Lint on node 20.x and ubuntu-latest:
src/components/MDX/Sandpack/generatedHooksLint.ts#L209
'e' is defined but never used
|
|
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
|