chore: fix asset path again attempt #4 #28
rahuldkjaindeploy.yml
on: push
build
51s
deploy-preview
40s
deploy-production
0s
Annotations
10 warnings
|
build:
src/app/support/page.tsx#L51
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
|
|
build:
src/app/page.tsx#L195
React Hook useEffect has a complex expression in the dependency array. Extract it to a separate variable so it can be statically checked
|
|
build:
src/app/page.tsx#L194
React Hook useEffect has a complex expression in the dependency array. Extract it to a separate variable so it can be statically checked
|
|
build:
src/app/page.tsx#L193
React Hook useEffect has a complex expression in the dependency array. Extract it to a separate variable so it can be statically checked
|
|
build:
src/app/page.tsx#L192
React Hook useEffect has a complex expression in the dependency array. Extract it to a separate variable so it can be statically checked
|
|
build:
src/app/addons/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
|
|
build:
src/app/addons/page.tsx#L161
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
|
|
build:
src/app/addons/page.tsx#L113
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
|
|
build:
src/app/addons/page.tsx#L63
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
|
|
build:
src/app/addons/page.tsx#L53
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
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
preview-build-28-1
Expired
|
4.59 MB |
sha256:15284be69c7dc683bf07cbb35eedc2280e8ddaac3a7919e0a52c5303b66224ce
|
|