fix(lint): corregir 3 errores ESLint react-hooks en DesktopContextMen… #6
SwonDevAnnotations
1 error and 10 warnings
|
Lint & Tests
Process completed with exit code 1.
|
|
Lint & Tests:
src/components/links/RichLinkCard.tsx#L113
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 & Tests:
src/components/layout/Header.tsx#L216
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 & Tests:
src/components/kanban/KanbanLinkListWidget.tsx#L41
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 & Tests:
src/components/desktop/DesktopContextMenu.tsx#L17
'Settings' is defined but never used. Allowed unused vars must match /^_/u
|
|
Lint & Tests:
src/components/command-palette/CommandPalette.tsx#L428
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 & Tests:
src/components/bento/BentoGrid.tsx#L224
React Hook useMemo has an unnecessary dependency: 'linkTags'. Either exclude it or remove the dependency array
|
|
Lint & Tests:
src/components/bento/BentoCard.tsx#L180
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 & Tests:
src/components/bento/BentoCard.tsx#L168
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 & Tests:
src/app/shared/[token]/SharedCollectionView.tsx#L141
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 & Tests:
src/app/shared/[token]/SharedCollectionView.tsx#L125
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
|