eslint/no-alert Restriction

What it does

Disallow the use of alert, confirm, and prompt

Why is this bad?

JavaScript’s alert, confirm, and prompt functions are widely considered to be obtrusive as UI elements and should be replaced by a more appropriate custom UI implementation. Furthermore, alert is often used while debugging code, which should be removed before deployment to production.

Examples

Examples of incorrect code for this rule:

alert("here!");

confirm("Are you sure?");

prompt("What's your name?", "John Doe");

Examples of correct code for this rule:

customAlert("Something happened!");

customConfirm("Are you sure?");

customPrompt("Who are you?");

function foo() {
  var alert = myCustomLib.customAlert;
  alert();
}

How to use

To enable this rule in the CLI or using the config file, you can use:

CLI

oxlint --deny no-alert

Config (.oxlintrc.json)

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

References

• Rule Source