Skip to content

Merge pull request #926 from rahuldkjain/rahuldkjain/full-revamp #21

Merge pull request #926 from rahuldkjain/rahuldkjain/full-revamp

Merge pull request #926 from rahuldkjain/rahuldkjain/full-revamp #21

Triggered via push October 15, 2025 15:21
Status Cancelled
Total duration 1m 35s
Artifacts 1

deploy.yml

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

Annotations

3 errors and 10 warnings
deploy-preview
The operation was canceled.
deploy-preview
The run was canceled by @rahuldkjain.
Build and Deploy
The run was canceled by @rahuldkjain.
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-21-1 Expired
4.59 MB
sha256:8452ce28d5bb3ff45df97e8e1913ee2344ef8689d82a0f6bc2a8dd99a263fad6