Keep the Javascript console clean

Rule from javascript under compatibility category

What is a trooper!

we have submitted your edit to the community for review! We'll review and make it live on the site in the next few hours, the internet thanks you :).

Browse another section of the knowledge base

Suggest an edit


This rule has no content... yet.

Add content to this rule

Or just browse to view rules that have content


Leaving debugging code in production is generally a bad idea. Also: the console object might not always be available (especially in older browsers).

// BAD:
if (err) {
  console.log('This should\'t happen!');

How do I fix this ?

  • Manually remove console.log statements
  • Use JSLing/JSHint/ESLint (or!) to notify you of missed console.log statements.
  • Use your build tools to remove console.log statements from production code.


Browse another section of the knowledge base

Signup icon
Ready to see how well your site scores?

Passmarked works best when you have an account. It allows you to keep a dashboard with saved data of the sites you have run through the system, we’ll alert you about important updates and you get access to the Passmarked Slack forum.

Sign up to get started