Avoid leaving console debug statements
このページは日本語には対応しておりません。随時翻訳に取り組んでいます。
翻訳に関してご質問やご意見ございましたら、
お気軽にご連絡ください。
ID: javascript-best-practices/no-console
Language: JavaScript
Severity: Warning
Category: Best Practices
Description
Debugging with console (such as console.log or console.info) is not considered a bad practice, but these statements can be accidentally left in production code, leading to unnecessary log pollution. It is important to remove or replace these debugging statements to maintain clean and secure production builds.
Non-Compliant Code Examples
console.log(foo) // General-purpose logging which can expose internal information
console.error(foo) // Error logging which can expose sensitive information
console.info(foo) // Informational logging which can clutter production logs
console.warn(foo) // Warning logging which can be excessive for production
Compliant Code Examples
Console.info(foo) // Example placeholder for a custom logging method or library
