[📝CUSTOM]Refactor ESLint Configuration for Stable Production Deployments (Level 3)

[sashreek-x]

Our existing ESLint setup can occasionally trigger unnecessary warnings or build conflicts in CI/CD environments (e.g., Vercel, GitHub Actions).

Proposed Solution

• Introduce environment-specific linting (frontend & backend separation)
• Use ESM imports for all plugins and configs
• Add safe default ignores (.vercel, dist, node_modules)
• Adjust rule severity levels to prevent deployment interruption

Expected Outcome
A streamlined, zero-error ESLint configuration fully compatible with Vite + React + Node environments.

[github-actions]

💡 Hi @sashreek-x! Thanks for your continued contributions! We appreciate your efforts and suggestions. Keep up the great work! 🚀

[sashreek-x]

Implemented a hardened, deployment-safe ESLint configuration in PR #904 — ensures smoother builds, React version auto-detection, and zero conflicts during deployment. Requesting assignment for validation and merge.

[Shailaja-poojari]

Hi! I found your project really interesting. Could you please let me know if there are any open issues that I can work on? I’d love to contribute and help solve one.