disallow the use of debugger (no-debugger)

The "extends": "eslint:recommended" property in a configuration file enables this rule.

The debugger statement is used to tell the executing JavaScript environment to stop execution and start up a debugger at the current point in the code. This has fallen out of favor as a good practice with the advent of modern debugging and development tools. Production code should definitely not contain debugger, as it will cause the browser to stop executing code and open an appropriate debugger.

Rule Details

This rule disallows debugger statements.

Example of incorrect code for this rule:

/*eslint no-debugger: "error"*/

function isTruthy(x) {
    debugger;
    return Boolean(x);
}

Example of correct code for this rule:

/*eslint no-debugger: "error"*/

function isTruthy(x) {
    return Boolean(x); // set a breakpoint at this line
}

When Not To Use It

If your code is still very much in development and don’t want to worry about stripping debugger statements, then turn this rule off. You’ll generally want to turn it back on when testing code prior to deployment.

Further Reading

• Debugger

Related Rules

• no-alert
• no-console

Version

This rule was introduced in ESLint 0.0.2.

Resources

• Rule source
• Documentation source