Skip to content

chore(deps): refresh package-lock.json to unblock npm ci in CI #31

chore(deps): refresh package-lock.json to unblock npm ci in CI

chore(deps): refresh package-lock.json to unblock npm ci in CI #31

Triggered via push July 2, 2026 22:59
Status Success
Total duration 2m 7s
Artifacts

ci.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 11 warnings
verify: app/[locale]/(public)/p/[slug]/page.tsx#L40
Unexpected any. Specify a different type
verify: app/[locale]/(public)/courses/page.tsx#L106
Unexpected any. Specify a different type
verify: app/[locale]/(public)/courses/page.tsx#L98
Unexpected any. Specify a different type
verify: app/[locale]/(public)/courses/page.tsx#L97
Unexpected any. Specify a different type
verify: app/[locale]/(public)/courses/page.tsx#L84
Unexpected any. Specify a different type
verify: app/[locale]/(public)/courses/page.tsx#L74
'productMap' is never reassigned. Use 'const' instead
verify: app/[locale]/(public)/courses/[id]/page.tsx#L142
Unexpected any. Specify a different type
verify: app/[locale]/(public)/courses/[id]/page.tsx#L128
Unexpected any. Specify a different type
verify: app/[locale]/(public)/courses/[id]/page.tsx#L97
Unexpected any. Specify a different type
verify: app/[locale]/(public)/checkout/page.tsx#L91
Unexpected any. Specify a different type
verify
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
verify: app/[locale]/dashboard/admin/categories/page.tsx#L3
'getUserRole' is defined but never used
verify: app/[locale]/dashboard/admin/billing/upgrade/page.tsx#L7
't' is assigned a value but never used
verify: app/[locale]/(public)/pricing/page.tsx#L11
'Plan' is defined but never used
verify: app/[locale]/(public)/page.tsx#L141
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
verify: app/[locale]/(public)/page.tsx#L77
't' is assigned a value but never used
verify: app/[locale]/(public)/page.tsx#L24
'Lock' is defined but never used
verify: app/[locale]/(public)/creators/page.tsx#L18
'Minus' is defined but never used
verify: app/[locale]/(public)/courses/[id]/page.tsx#L307
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
verify: app/[locale]/(public)/courses/[id]/page.tsx#L279
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
verify: app/[locale]/(public)/courses/[id]/page.tsx#L181
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