自动发布版本 #17
huzhengenAnnotations
3 errors and 6 warnings
|
lint:
src/shared/hooks/useAppConfig.js#L1
Header does not include expected content
|
|
lint:
src/shared/utils/app.js#L1
Header does not include expected content
|
|
lint
Process completed with exit code 1.
|
|
lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
lint:
src/app/home/Contributor.js#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
|
|
lint:
src/app/oauth/page.js#L89
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
|
|
lint:
src/app/shilling/[id]/page.js#L176
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
|
|
lint:
src/app/u/[handle]/Banner.js#L75
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
|
|
lint:
src/entry/components/Header/CustomConnectButton.js#L137
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
|