Skip to content

chore: update demo link with V2 #32

chore: update demo link with V2

chore: update demo link with V2 #32

Triggered via push October 16, 2025 09:24
Status Success
Total duration 1m 36s
Artifacts 1

deploy.yml

on: push
deploy-preview
22s
deploy-preview
deploy-production
0s
deploy-production
Fit to window
Zoom out
Zoom in

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-32-1 Expired
4.59 MB
sha256:0b017121e5f145026c0f27af8a87509f365ddad1a7158e97df76f7f33cdde37f