Feat/coverage #24
codesailor4frontend-ci.yml
on: pull_request
Frontend Lint, Type-Check & Build
36s
Annotations
1 error and 11 warnings
|
Frontend Lint, Type-Check & Build
Process completed with exit code 1.
|
|
Frontend Lint, Type-Check & Build
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: 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/
|
|
Frontend Lint, Type-Check & Build:
frontend/hooks/useWebSocket.ts#L85
React Hook useCallback has an unnecessary dependency: 'options.userId'. Either exclude it or remove the dependency array
|
|
Frontend Lint, Type-Check & Build:
frontend/components/ui/command-palette.tsx#L92
The 'results' array makes the dependencies of useCallback Hook (at line 125) change on every render. To fix this, wrap the initialization of 'results' in its own useMemo() Hook
|
|
Frontend Lint, Type-Check & Build:
frontend/components/ui/avatar.tsx#L6
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
|
|
Frontend Lint, Type-Check & Build:
frontend/components/qr-scanner.tsx#L62
React Hook useEffect has a missing dependency: 'scanning'. Either include it or remove the dependency array
|
|
Frontend Lint, Type-Check & Build:
frontend/components/assets/photo-gallery.tsx#L82
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
|
|
Frontend Lint, Type-Check & Build:
frontend/components/assets/photo-gallery.tsx#L60
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
|
|
Frontend Lint, Type-Check & Build:
frontend/app/scan/[assetId]/page.tsx#L73
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
|
|
Frontend Lint, Type-Check & Build:
frontend/app/(dashboard)/my-assets/page.tsx#L66
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
|
|
Frontend Lint, Type-Check & Build:
frontend/app/(dashboard)/assets/page.tsx#L189
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
|
|
Frontend Lint, Type-Check & Build:
frontend/app/(dashboard)/assets/[id]/page.tsx#L532
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
|