News articles, privacy/terms, LinkedIn, images, object-contain, dev w… #1
AdamKaniastyAnnotations
10 errors and 10 warnings
|
build:
src/components/MissionSection.tsx#L30
`'` can be escaped with `'`, `‘`, `'`, `’`
|
|
build:
src/components/MissionSection.tsx#L30
`"` can be escaped with `"`, `“`, `"`, `”`
|
|
build:
src/components/MissionSection.tsx#L30
`"` can be escaped with `"`, `“`, `"`, `”`
|
|
build:
src/app/projects/[id]/not-found.tsx#L15
`'` can be escaped with `'`, `‘`, `'`, `’`
|
|
build:
src/app/projects/[id]/not-found.tsx#L15
`'` can be escaped with `'`, `‘`, `'`, `’`
|
|
build:
src/app/news/[id]/not-found.tsx#L16
`'` can be escaped with `'`, `‘`, `'`, `’`
|
|
build:
src/app/news/[id]/not-found.tsx#L16
`'` can be escaped with `'`, `‘`, `'`, `’`
|
|
build:
src/app/join-us/page.tsx#L133
`'` can be escaped with `'`, `‘`, `'`, `’`
|
|
build:
src/app/join-us/page.tsx#L132
`'` can be escaped with `'`, `‘`, `'`, `’`
|
|
build:
src/app/join-us/page.tsx#L129
`'` can be escaped with `'`, `‘`, `'`, `’`
|
|
build:
src/components/Navbar.tsx#L152
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
|
|
build:
src/components/Navbar.tsx#L112
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
|
|
build:
src/components/Navbar.tsx#L81
'isMobile' is assigned a value but never used
|
|
build:
src/components/Logo.tsx#L48
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
|
|
build:
src/components/Logo.tsx#L36
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
|
|
build:
src/components/Logo.tsx#L31
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
|
|
build:
src/components/Logo.tsx#L25
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
|
|
build:
src/components/Logo.tsx#L16
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
|
|
build:
src/components/ContactForm.tsx#L45
'error' is defined but never used
|
|
build:
src/app/page.tsx#L3
'Section' is defined but never used
|