📝[Docs]: Apply ESLint and Prettier formatting to entire codebase

[sheikhlimon]

Is there an existing issue for this?

• I have searched the existing issues

Issue Description

Description

After merging PR #805 (ESLint/Prettier configuration), we need to apply the formatting rules to the entire codebase in a separate commit.

Context

The ESLint and Prettier configuration has been added, but no code has been reformatted yet. This keeps the configuration PR reviewable and separates tooling changes from code changes.

Tasks

• Pull the latest changes from main branch
• Run npm install to ensure all dependencies are installed
• Run npm run lint:fix to auto-fix linting issues
• Run npm run format to format all code files
• Verify build succeeds with npm run build
• Review the changes to ensure no code logic was broken

Files Affected

• All .js, .jsx, .ts, .tsx files
• All .json and .css files
• NOT markdown/MDX files (protected by .prettierignore)

Suggested Change

This will format approximately 107+ files with:

• Consistent indentation (2 spaces)
• double quotes instead of single quotes
• Consistent semicolon usage
• Proper line breaks and spacing

Commands to Run

npm run lint:fix && npm run format
npm run build

Rationale

• The diff will be large but should only contain formatting changes, no logic changes
• This is a one-time operation - future PRs will have minimal formatting diffs
• Documentation files are excluded to preserve MDX syntax

Urgency

Medium

Record

• I have read the Contributing Guidelines
• Are you a GSSOC'25 contributor
• I want to work on this issue

[github-actions]

Thanks for opening this issue! 🎉 We'll look into it as soon as possible, estimated time for response is 5–8 hrs.

Don't raise PR unless assigned to you.

In the meantime, please provide all necessary details and context to your issue — screenshots or videos of your changes help 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 issue 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 contributions are eligible for sponsorship 💰

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

📚Resources which can help you know more about Github 👇🏻

1. End to End GitHub Beginner Playlist: GitHub Playlist.

2. Build your GitHub Profile: GitHub Profile Optimisation.

3. GitHub Handbook for dummies: GitHub Blog for Beginners.

[github-actions]

👤 Issue assigned to @sheikhlimon.