Avoid leaving console debug statements

Docs > Code Analysis > Static Analysis Rules > Avoid leaving console debug statements

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Metadata

ID: typescript-best-practices/no-console

Language: TypeScript

Severity: Warning

Category: Best Practices

Description

Debugging with console is not considered a bad practice, but it’s easy to forget about console statements and leave them in production code. There is no need to pollute production builds with debugging statements.

Non-Compliant Code Examples

console.log(foo)
console.error(foo)
console.info(foo)
console.warn(foo)

Compliant Code Examples

Console.info(foo)

How to use this rule

1
2
rulesets:
  - typescript-best-practices     # Rules to enforce TypeScript best practices.

Create a static-analysis.datadog.yml with the content above at the root of your repository
Use our free IDE Plugins or add Code Analysis scans to your CI pipelines
Get feedback on your code

For more information, please read the Code Analysis documentation

VS Code Extension

Identify code vulnerabilities directly in your
VS Code editor

JetBrains Plugin

Identify code vulnerabilities directly in
JetBrains products