remove deprecated env #341
nialexsanAnnotations
4 errors and 7 warnings
|
Static checks (20.x):
types/cdc.d.ts#L1
Replace `'*.cdc'` with `"*.cdc"`
|
|
Static checks (20.x):
types/cdc.d.ts#L2
Delete `;`
|
|
Static checks (20.x):
types/cdc.d.ts#L3
Delete `;`
|
|
Static checks (20.x)
Process completed with exit code 1.
|
|
Static checks (20.x)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Static checks (20.x):
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
|
|
Static checks (20.x):
components/LoadingFeedback.tsx#L24
img elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
|
Static checks (20.x):
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
|
|
Static checks (20.x):
components/SidebarAccordion.tsx#L142
img elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
|
Static checks (20.x):
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
|
|
Tests (20.x)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|