Stop Accidentally Shipping console.log: One ESLint Rule to Clean Your Production Code

Ever pushed code only to discover a stray console.log() made it into production? You can prevent that without altering your workflow or habits by adding a single ESLint rule.

Ultimate solution: one ESLint rule

{
  "rules": {
    "no-console": "warn"
  }
}

With this configuration, any forgotten console.log() triggers an immediate warning, ensuring it never slips into production.

Why it works

Block accidental logs from reaching production.

Reduce PR noise : everyone sees a clean diff.

Local testing : you can still use logs, just remove them before committing.

Want stricter enforcement?

{
  "rules": {
    "no-console": "error"
  }
}

This setting will fail the commit until all console statements are removed.

Bonus: automatically strip them

Combine husky and lint-staged to run ESLint as a pre‑commit hook, catching any stray logs before they are committed – a lifesaver for careless team members.

Keep logs only in development

if (process.env.NODE_ENV !== 'production') {
  console.log('Debug info');
}

Use conditional logging to retain useful debug output during development while keeping production quiet.

Lint rules are more than style checks; they act as habit correctors, helping you avoid dirty logs, noisy PR comments, and the embarrassment of “I forgot the logs”. Try it and thank yourself later.