Feature/christenjack/auth #100
jackavhAnnotations
1 error and 11 warnings
|
Frontend check
Process completed with exit code 1.
|
|
Frontend check
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/.
|
|
Frontend check:
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
|
|
Frontend check:
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
|
|
Frontend check:
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
|
|
Frontend check:
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
|
|
Frontend check:
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
|
|
Frontend check:
frontend/src/app/admin/mailing-list/page.tsx#L78
'handleCopyEmails' was used before it was defined
|
|
Frontend check:
frontend/src/app/admin/mailing-list/page.tsx#L78
'handleEmailHover' was used before it was defined
|
|
Frontend check:
frontend/src/app/admin/mailing-list/page.tsx#L353
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
|
|
Frontend check:
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
|
|
Frontend check:
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
|