Skip to content

chore: update package-lock.json for dependency management #12

chore: update package-lock.json for dependency management

chore: update package-lock.json for dependency management #12

Triggered via push December 16, 2025 20:00
Status Failure
Total duration 38s
Artifacts

build-test.yml

on: push
Build, Test & Push Image
34s
Build, Test & Push Image
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 8 warnings
Build, Test & Push Image: app/account/recently-viewed/page.tsx#L77
Do not use an `<a>` element to navigate to `/components/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages
Build, Test & Push Image: app/account/notifications/page.tsx#L211
`'` can be escaped with `&apos;`, `&lsquo;`, `&#39;`, `&rsquo;`
Build, Test & Push Image: app/account/notifications/page.tsx#L18
'user' is assigned a value but never used
Build, Test & Push Image: app/account/addresses/page.tsx#L8
'deleteAddress' is assigned a value but never used
Build, Test & Push Image: app/account/addresses/page.tsx#L8
'updateAddress' is assigned a value but never used
Build, Test & Push Image: app/account/addresses/page.tsx#L8
'addAddress' is assigned a value but never used
Build, Test & Push Image: app/about/page.tsx#L117
`'` can be escaped with `&apos;`, `&lsquo;`, `&#39;`, `&rsquo;`
Build, Test & Push Image: app/about/page.tsx#L82
'index' is defined but never used
Build, Test & Push Image: app/about/page.tsx#L21
`'` can be escaped with `&apos;`, `&lsquo;`, `&#39;`, `&rsquo;`
Build, Test & Push Image: app/500/page.tsx#L48
`'` can be escaped with `&apos;`, `&lsquo;`, `&#39;`, `&rsquo;`
Build, Test & Push Image: app/wishlist/page.tsx#L74
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, Test & Push Image: app/product/[id]/page.tsx#L342
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, Test & Push Image: app/product/[id]/page.tsx#L96
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, Test & Push Image: app/layout.tsx#L24
Custom fonts not added in `pages/_document.js` will only load for a single page. This is discouraged. See: https://nextjs.org/docs/messages/no-page-custom-font
Build, Test & Push Image: app/components/ui/ProductCard.tsx#L48
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, Test & Push Image: app/cart/page.tsx#L70
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, Test & Push Image: app/builderbot/page.tsx#L226
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, Test & Push Image: app/admin/products/[id]/page.tsx#L413
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