feat: add VS Code workspace settings for consistent editor setup

[sheikhlimon]

Description

This PR addresses the previously raised feature request to standardize the development environment. While a .devcontainer was considered, this approach was not implemented, even though Docker and Docker Compose are fully functional on the project.

Reasoning

• .devcontainer introduces additional complexity for contributors who may not want or need to use Docker for local development.
• The dev container approach caused potential issues with Docker image availability and startup times.
• Node.js, npm, and other dependencies are already expected to be installed locally by contributors.
• The primary goal—automatic setup of editor extensions and consistent formatting—can be achieved without a container.

Fixes #830

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):

Changes Made

Changes Made

• Added .vscode/extensions.json to recommend essential extensions: Prettier, ESLint, and Tailwind CSS.
• Added .vscode/settings.json to enforce consistent editor settings:
  • editor.formatOnSave: true
  • editor.tabSize: 2
  • files.eol: "\n"
• Added .prettierrc on Eslint format code PR to ensure consistent formatting rules across all contributors.

Benefits

• Contributors automatically get recommended extensions and workspace settings without Docker.
• Reduces onboarding friction for new contributors.
• Ensures consistent formatting and editor behavior across the project.

Testing

1. Open the project in VS Code.
2. Confirm recommended extensions are suggested (Prettier, ESLint, Tailwind CSS).
3. Verify editor settings are applied correctly (tab size, EOL, format on save).
4. Save a file and confirm Prettier formats according to .prettierrc rules.

Dependencies

• n/a
• n/a

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:

• enhancement
• level 1
• recode
• hacktoberfest-accepted

Assignees:

• sheikhlimon

Milestones:

• recode:launch 3.0

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
recode-website	Ready	Preview	Comment	Oct 8, 2025 9:37am