Make cmd+click open new tab only in sidebar #279
ctateAnnotations
10 warnings
|
checks:
components/file-browser.tsx#L152
The 'currentViewData' logical expression could make the dependencies of useCallback Hook (at line 621) change on every render. To fix this, wrap the initialization of 'currentViewData' in its own useMemo() Hook
|
|
checks:
components/file-browser.tsx#L152
The 'currentViewData' logical expression could make the dependencies of useCallback Hook (at line 542) change on every render. To fix this, wrap the initialization of 'currentViewData' in its own useMemo() Hook
|
|
checks:
components/file-browser.tsx#L152
The 'currentViewData' logical expression could make the dependencies of useCallback Hook (at line 424) change on every render. To fix this, wrap the initialization of 'currentViewData' in its own useMemo() Hook
|
|
checks:
components/file-browser.tsx#L152
The 'currentViewData' logical expression could make the dependencies of useCallback Hook (at line 366) change on every render. To fix this, wrap the initialization of 'currentViewData' in its own useMemo() Hook
|
|
checks:
app/repos/new/page.tsx#L361
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
|
|
checks:
app/repos/new/page.tsx#L356
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
|
|
checks:
app/repos/new/page.tsx#L316
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
|
|
checks:
app/repos/new/page.tsx#L311
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
|
|
checks:
app/repos/new/page.tsx#L246
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
|
|
checks:
app/repos/new/page.tsx#L238
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
|