Feature/christenjack/storage #129
Annotations
10 errors and 11 warnings
|
Run npm ci --legacy-peer-deps:
frontend/src/app/admin/page-editor/page.tsx#L4
'ImageDisplay' is defined but never used. Allowed unused vars must match /^_/u
|
|
Run npm ci --legacy-peer-deps:
frontend/src/app/admin/page-editor/page.tsx#L4
Unable to resolve path to module '@/components/admin/imageStorage/GalleryDisplay'
|
|
Run npm ci --legacy-peer-deps:
frontend/src/app/admin/page-editor/team/page.tsx#L40
'Collapsable' is not defined
|
|
Run npm ci --legacy-peer-deps:
frontend/src/app/admin/page-editor/team/page.tsx#L48
Unsafe assignment of an `any` value
|
|
Run npm ci --legacy-peer-deps:
frontend/src/app/admin/page-editor/team/page.tsx#L48
Unsafe member access .OUR_MISSION on an `any` value
|
|
Run npm ci --legacy-peer-deps:
frontend/src/app/admin/page-editor/team/page.tsx#L50
'Collapsable' is not defined
|
|
Run npm ci --legacy-peer-deps:
frontend/src/app/admin/page-editor/team/page.tsx#L55
Unsafe assignment of an `any` value
|
|
Run npm ci --legacy-peer-deps:
frontend/src/app/admin/page-editor/team/page.tsx#L55
Unsafe member access .OUR_TEAM on an `any` value
|
|
Run npm ci --legacy-peer-deps:
frontend/src/components/ImageDisplay.tsx#L4
'useState' is defined but never used. Allowed unused vars must match /^_/u
|
|
Run npm ci --legacy-peer-deps:
frontend/src/components/ImageDropzone.tsx#L3
'useEffect' is defined but never used. Allowed unused vars must match /^_/u
|
|
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 --legacy-peer-deps:
frontend/src/app/(web app)/newsletter/[newsletterID]/page.tsx#L72
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 --legacy-peer-deps:
frontend/src/app/(web app)/newsletter/[newsletterID]/page.tsx#L93
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 --legacy-peer-deps:
frontend/src/app/(web app)/newsletter/[newsletterID]/page.tsx#L104
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 --legacy-peer-deps:
frontend/src/app/(web app)/newsletter/page.tsx#L29
'loadNewspapers' was used before it was defined
|
|
Run npm ci --legacy-peer-deps:
frontend/src/app/(web app)/newsletter/page.tsx#L30
'loadPageMap' was used before it was defined
|
|
Run npm ci --legacy-peer-deps:
frontend/src/app/(web app)/page.tsx#L77
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 --legacy-peer-deps:
frontend/src/app/admin/mailing-list/page.tsx#L78
'handleCopyEmails' was used before it was defined
|
|
Run npm ci --legacy-peer-deps:
frontend/src/app/admin/mailing-list/page.tsx#L78
'handleEmailHover' was used before it was defined
|
|
Run npm ci --legacy-peer-deps:
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
|
|
Run npm ci --legacy-peer-deps:
frontend/src/app/admin/newsletter-creator/page.tsx#L296
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
|
Loading