Feature/purchase/item prices #54
Merged
Annotations
10 errors and 5 warnings
|
Run ESLint
Unexpected any. Specify a different type
|
|
Run ESLint
Unexpected any. Specify a different type
|
|
Run ESLint
Unexpected any. Specify a different type
|
|
Run ESLint:
src/contexts/CartContext.tsx#L109
Unexpected any. Specify a different type
|
|
Run ESLint:
src/contexts/CartContext.tsx#L100
Unexpected any. Specify a different type
|
|
Run ESLint:
src/contexts/CartContext.tsx#L89
Unexpected any. Specify a different type
|
|
Run ESLint:
src/components/SearchableSelect.tsx#L9
Unexpected any. Specify a different type
|
|
Run ESLint:
src/components/LoginForm.tsx#L31
Unexpected any. Specify a different type
|
|
Run ESLint:
src/app/page.tsx#L67
Unexpected any. Specify a different type
|
|
Run ESLint:
src/app/page.tsx#L50
Unexpected any. Specify a different type
|
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run ESLint:
src/services/api.ts#L156
'unitPrice' is assigned a value but never used
|
|
Run ESLint:
src/contexts/AuthContext.tsx#L102
'err' is defined but never used
|
|
Run ESLint:
src/contexts/AuthContext.tsx#L64
'err' is defined but never used
|
|
Run ESLint:
src/app/about/page.tsx#L55
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
|
background
wait
wait-all
cancel
Loading