chore: apply ESLint and Prettier formatting across codebase

[sheikhlimon]

Description

• ESLint and Prettier configuration was added in PR feat: add ESLint & Prettier configuration #805 (feat/add-eslint-setup).
• That PR only added the config to keep it reviewable, without applying formatting to the codebase.

Fixes #807

Type of Change

• New feature (e.g., new page, component, or functionality)
• Bug fix (non-breaking change that fixes an issue)
• UI/UX improvement (design, layout, or styling updates)
• Performance optimization (e.g., code splitting, caching)
• Documentation update (README, contribution guidelines, etc.)
• Other (please specify): Linting and Formatting

Changes Made

• Cherry-picked the ESLint/Prettier configuration from feat/add-eslint-setup
• Ran npm run lint:fix and npm run format across all .js, .jsx, .ts, .tsx, .json, and .css files
• Ensured that Markdown/MDX files remain untouched (.prettierignore)
• Large diff (~159+ files) contains only formatting changes — no code logic has been altered

Dependencies

• No new dependencies were added; all ESLint/Prettier packages come from feat: add ESLint & Prettier configuration #805.

Checklist

• My code follows the style guidelines of this project.
• I have tested my changes across major browsers and devices
• My changes do not generate new console warnings or errors .
• I ran npm run build and attached screenshot(s) in this PR.
• This is already assigned Issue to me, not an unassigned issue.

[vercel]

@sheikhlimon is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

1. Get free Consultation use code recode50 to get free: Mentorship for free.

2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

[github-actions]

Synced data from Linked Issues

Labels:

• don't-merge
• level 1
• under review
• recode
• hacktoberfest-accepted
• enhancement

Assignees:

• sheikhlimon

Milestones:

• recode:launch 3.0

[sheikhlimon]

@iitzIrFan This PR applies the ESLint and Prettier formatting to the entire codebase using the config from #805. All formatting changes are automatic and no code logic has been changed. This ensures future PRs will have minimal lint/format diffs.
Thanks for reviewing!

[iitzIrFan]

@sheikhlimon Thanks for your efforts will review and update if, needs any changes :)

[sheikhlimon]

@sanjay-kv This probably marks my 15th PR! 🎉
Thank you so much for the encouragement. I really appreciate it.
I haven’t been able to work on the UI yet since the docs needed a bit more love, but I did manage to set up some configs.
I’m planning to focus on the UI next. I’m still learning, but I’ll learn as I go!

[Adez017]

163 file changes , i think this might be a big task and its not appropriate to accept all the chnages without verifying . i request @sanjay-kv @iitzIrFan to look into this .