fix: lint issues blocking Merge Action

[CarreraPHP]

Disable Eslint for code that is not supported by Eslint & also add key prop for the component within map function issues in code,

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
19-react-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 13, 2024 2:25pm
react-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 13, 2024 2:25pm

[github-actions]

Size changes

Details

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

Five Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load
/404	104.29 KB (🟡 +10 B)	208.48 KB
/500	104.28 KB (🟡 +10 B)	208.47 KB
/[[...markdownPath]]	106.13 KB (🟡 +10 B)	210.32 KB
/errors	104.49 KB (🟡 +10 B)	208.69 KB
/errors/[errorCode]	104.47 KB (🟡 +10 B)	208.67 KB

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 10% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

[Neoxs]

🚀 Just completed an ESLint v9 migration, and wow… what a ride! 😵‍💫

I ran into breaking changes, weird errors, and unexpected surprises—but I documented everything so you don’t have to suffer the same way.

If you’re upgrading (or still hesitating), this guide might save you some headaches:
📖 neoxs.me/blog/migration-to-eslint-v9