fix: upgrade eslint #422
longsizhuoAnnotations
3 errors and 8 warnings
|
build
Process completed with exit code 1.
|
|
build:
scripts/compute-svg-bbox.js#L1
A `require()` style import is forbidden
|
|
build:
app/components/Footer.tsx#L50
Do not use an `<a>` element to navigate to `/docs/ai/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages
|
|
build:
scripts/move-doc-images.mjs#L206
'e' is defined but never used
|
|
build:
scripts/move-doc-images.mjs#L161
'e' is defined but never used
|
|
build:
scripts/check-images.mjs#L115
'routePath' is assigned a value but never used
|
|
build:
eslint.config.mjs#L12
Assign array to a variable before exporting as module default
|
|
build:
app/components/LicenseNotice.tsx#L52
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
|
|
build:
app/components/LicenseNotice.tsx#L42
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
|
|
build:
app/components/LicenseNotice.tsx#L32
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
|
|
build:
app/components/LicenseNotice.tsx#L22
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
|