refactor: remove billing plan properties #228
Merged
Annotations
10 warnings
|
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
|
|
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
|
|
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
|
|
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
|
|
app/repos/new/page.tsx#L325
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
|
|
app/repos/new/page.tsx#L320
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
|
|
app/repos/new/page.tsx#L280
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
|
|
app/repos/new/page.tsx#L275
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
|
|
app/repos/new/page.tsx#L210
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
|
|
app/repos/new/page.tsx#L202
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
|
The logs for this run have expired and are no longer available.
Loading