Create no-console-in-prod.js

[anuragchvn-blip]

🚀 Feature: Restrict console.log() in Production

Summary

This PR introduces a custom ESLint rule no-console-in-prod that prevents accidental console.log() usage in production environments while allowing it during development. This aligns with Airbnb’s best practices for writing clean and maintainable JavaScript.

🔍 Changes Introduced

• Added a new ESLint rule: no-console-in-prod.js inside packages/eslint-config-airbnb/lib/rules/.
• Configured ESLint to:
  • Warn about console.log() in development.
  • Throw an error if console.log() is found in production (NODE_ENV=production).
• Updated index.js to include the new rule.

🛠️ Implementation Details

The rule checks for console.log() calls and enforces the following:

• 🚨 Error in Production: "console.log() is not allowed in production. Use a proper logger instead."
• ⚠️ Warning in Development: "Consider removing console.log() before pushing to production."

✅ Why This is Valuable

✔ Enhances Airbnb’s JavaScript standards by preventing unnecessary console logs in production.
✔ Encourages developers to use structured logging solutions (e.g., Winston, Bunyan).
✔ Improves security and performance by avoiding excessive logging in production.

🧪 Testing

• Tested locally using ESLint on sample files.
• Verified that it correctly warns in development and throws errors in production.

🔗 References

• Airbnb JavaScript Style Guide

Would love to hear feedback and suggestions from the maintainers! 🚀

[ljharb]

These packages are configs, not plugins, and can't contain rules.

Also, console.log is perfectly fine in production on the server.