Feature/christenjacob/donationsflow #66
Annotations
10 errors and 11 warnings
|
Run npm ci:
frontend/src/api/payments.ts#L3
'APIResult' is defined but never used. Allowed unused vars must match /^_/u
|
|
Run npm ci:
frontend/src/api/payments.ts#L9
'response' is assigned a value but never used. Allowed unused vars must match /^_/u
|
|
Run npm ci:
frontend/src/api/payments.ts#L11
Unsafe assignment of an `any` value
|
|
Run npm ci:
frontend/src/app/layout.tsx#L1
'PayPalScriptProvider' is defined but never used. Allowed unused vars must match /^_/u
|
|
Run npm ci:
frontend/src/components/payment/AmountPicker.tsx#L8
Unsafe assignment of an `any` value
|
|
Run npm ci:
frontend/src/components/payment/AmountPicker.tsx#L63
Expected an assignment or function call and instead saw an expression
|
|
Run npm ci:
frontend/src/components/payment/DonateForm.tsx#L4
'AmountPicker' is defined but never used. Allowed unused vars must match /^_/u
|
|
Run npm ci:
frontend/src/components/payment/DonateForm.tsx#L8
'setProductId' is assigned a value but never used. Allowed unused elements of array destructuring patterns must match /^_/u
|
|
Run npm ci:
frontend/src/components/payment/DonationTypeSelection.tsx#L25
Returning a void expression from an arrow function shorthand is forbidden. Please add braces to the arrow function
|
|
Run npm ci:
frontend/src/components/payment/DonationTypeSelection.tsx#L44
Returning a void expression from an arrow function shorthand is forbidden. Please add braces to the arrow function
|
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Run npm ci:
frontend/src/app/(web app)/newsletter/[newsletterID]/page.tsx#L84
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
|
|
Run npm ci:
frontend/src/app/(web app)/newsletter/[newsletterID]/page.tsx#L102
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
|
|
Run npm ci:
frontend/src/app/(web app)/newsletter/[newsletterID]/page.tsx#L118
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
|
|
Run npm ci:
frontend/src/app/(web app)/newsletter/[newsletterID]/page.tsx#L129
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
|
|
Run npm ci:
frontend/src/app/(web app)/page.tsx#L73
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
|
|
Run npm ci:
frontend/src/components/ContactInfoCard.tsx#L14
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
|
|
Run npm ci:
frontend/src/components/HeaderBar.tsx#L20
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
|
|
Run npm ci:
frontend/src/components/HeaderBar.tsx#L26
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
|
|
Run npm ci:
frontend/src/components/ValueCard.tsx#L15
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
|
|
Run npm ci:
frontend/src/components/payment/DonateApp.tsx#L3
There should be no empty line within import group
|
The logs for this run have expired and are no longer available.
Loading