fix tag #329
Annotations
4 errors and 7 warnings
Run npm run lint:
components/FundAccountSubmitted.tsx#L39
'_isFetchingBalance' is assigned a value but never used
|
Run npm run lint:
components/FundAccountSubmitted.tsx#L40
'_balance' is assigned a value but never used
|
Run npm run lint:
components/FundAccountSubmitted.tsx#L41
'_balanceError' is assigned a value but never used
|
Run npm run lint
Process completed with exit code 1.
|
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Run npm run lint:
components/Header.tsx#L32
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
Run npm run lint:
components/LoadingFeedback.tsx#L24
img elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
Run npm run lint:
components/LoadingFeedback.tsx#L24
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
Run npm run lint:
components/SidebarAccordion.tsx#L142
img elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
Run npm run lint:
components/SidebarAccordion.tsx#L142
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
Run npm run lint:
pages/api/account.ts#L16
Assign arrow function to a variable before exporting as module default
|
Loading