Skip to content

How to disable an ESLint rule

New Course Coming Soon:

Get Really Good at Git

A quick tutorial on how to disable ESLint rules

What can you do to disable one ESLint rule that is perhaps set automatically by your tooling?

Consider the case where your tooling set the no-debugger and no-console rules.

There might be a valid reason for production code, but in development mode, having the ability to access the browser debugger and the Console API is essential.

You can disable one or more specific ESLint rules for a whole file by adding on a few lines:

/* eslint-disable no-debugger, no-console */
console.log('test')

or you can just do so in a block, re-enabling it afterwards:

/* eslint-disable no-debugger, no-console */
console.log('test')
/* eslint-enable no-alert, no-console */

Or you can disable the rule on a specific line:

console.log('test') // eslint-disable-line no-console
debugger // eslint-disable-line no-debugger
alert('test') // eslint-disable-line no-alert

Another way is to disable it globally for the project.

In package.json you can find the eslintConfig rule, which might have some content already, like this:

  "eslintConfig": {
    "extends": [
      "react-app",
      "react-app/jest"
    ]
  },

Here you can disable the rules you want to disable:

  "eslintConfig": {
    "extends": [
      "react-app",
      "react-app/jest"
    ],
    "rules": {
      "no-unused-vars": "off"
    }
  },
Are you intimidated by Git? Can’t figure out merge vs rebase? Are you afraid of screwing up something any time you have to do something in Git? Do you rely on ChatGPT or random people’s answer on StackOverflow to fix your problems? Your coworkers are tired of explaining Git to you all the time? Git is something we all need to use, but few of us really master it. I created this course to improve your Git (and GitHub) knowledge at a radical level. A course that helps you feel less frustrated with Git. Launching Summer 2024. Join the waiting list!

Here is how can I help you: