Lint

Bump braces from 3.0.2 to 3.0.3 #56

Sign in to view logs

Triggered via pull request June 19, 2024 17:21

dependabot[bot]

opened #39

dependabot/npm_and_yarn/braces-3.0.3

Status Success

Total duration 1m 8s

Artifacts –

lint.yaml

on: pull_request

Annotations

51 warnings

src/components/Carousel.js#L27

React Hook useEffect has a missing dependency: 'content.length'. Either include it or remove the dependency array (react-hooks/exhaustive-deps)

src/components/CarouselItem.js#L4

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 (@next/next/no-img-element)

src/components/CarouselItem.js#L4

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/Footer.js#L19

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 (@next/next/no-img-element)

src/components/Footer.js#L19

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/Footer.js#L23

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 (@next/next/no-img-element)

src/components/Footer.js#L29

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 (@next/next/no-img-element)

src/components/Footer.js#L99

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 (@next/next/no-img-element)

src/components/Footer.js#L99

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/Footer.js#L108

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 (@next/next/no-img-element)

src/components/Footer.js#L108

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/Footer.js#L121

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 (@next/next/no-img-element)

src/components/Footer.js#L121

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/Footer.js#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 (@next/next/no-img-element)

src/components/Footer.js#L129

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/Footer.js#L137

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 (@next/next/no-img-element)

src/components/Footer.js#L137

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/Footer.js#L151

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 (@next/next/no-img-element)

src/components/Footer.js#L151

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/Footer.js#L165

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 (@next/next/no-img-element)

src/components/Footer.js#L165

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/Footer.js#L174

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 (@next/next/no-img-element)

src/components/Footer.js#L174

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/Footer.js#L189

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 (@next/next/no-img-element)

src/components/Footer.js#L189

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/HeaderNav.js#L58

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 (@next/next/no-img-element)

src/components/HeaderNav.js#L58

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/HeaderNav.js#L92

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 (@next/next/no-img-element)

src/components/HeaderNav.js#L92

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/HeaderNav.js#L94

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 (@next/next/no-img-element)

src/components/HeaderNav.js#L94

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/HeaderNav.js#L112

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 (@next/next/no-img-element)

src/components/HeaderNav.js#L112

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/HeaderNav.js#L114

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 (@next/next/no-img-element)

src/components/HeaderNav.js#L114

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/HeaderNavDropdown.js#L8

React Hook useEffect has a missing dependency: 'onHover'. Either include it or remove the dependency array. If 'onHover' changes too often, find the parent component that defines it and wrap that definition in useCallback (react-hooks/exhaustive-deps)

src/components/LeaderProfile.js#L6

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 (@next/next/no-img-element)

src/components/LeaderProfile.js#L6

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/LeaderProfile.js#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 (@next/next/no-img-element)

src/components/LeaderProfile.js#L15

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/MobileNav.js#L21

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 (@next/next/no-img-element)

src/components/MobileNav.js#L21

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/MobileNav.js#L27

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 (@next/next/no-img-element)

src/components/MobileNav.js#L27

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/MobileNav.js#L37

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 (@next/next/no-img-element)

src/components/MobileNav.js#L37

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/MobileNav.js#L60

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 (@next/next/no-img-element)

src/components/MobileNav.js#L60

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

src/components/MobileNav.js#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 (@next/next/no-img-element)

src/components/MobileNav.js#L72

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images (jsx-a11y/alt-text)

Run linters

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, wearerequired/lint-action@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.