chore: improve token preview in storefront #1552
Thunear
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
checks.yml
on: pull_request
Checks, builds and tests code
4m 34s
Annotations
6 warnings
|
Checks, builds and tests code:
packages/react/src/components/Select/Select.test.tsx#L43
'_o' is defined but never used
|
|
Checks, builds and tests code:
packages/react/src/components/Select/Select.test.tsx#L43
'_k' is defined but never used
|
|
Checks, builds and tests code:
packages/react/src/components/Select/utils.ts#L16
Forbidden non-null assertion
|
|
Checks, builds and tests code:
storefront/layouts/NavigationPageLayout/NavigationPageLayout.tsx#L11
'PageSection' is defined but never used
|
|
Checks, builds and tests code:
storefront/layouts/NotFoundLayout/NotFoundLayout.tsx#L16
'content' is defined but never used
|
|
Checks, builds and tests code:
storefront/layouts/NotFoundLayout/NotFoundLayout.tsx#L21
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|