eslint/no-eq-null Restriction

⚠️🛠️️ A dangerous auto-fix is available for this rule.

What it does

Disallow null comparisons without type-checking operators.

Why is this bad?

Comparing to null without a type-checking operator (== or !=), can have unintended results as the comparison will evaluate to true when comparing to not just a null, but also an undefined value.

Example

Examples of incorrect code for this rule:

if (foo == null) {
  bar();
}
if (baz != null) {
  bar();
}

Examples of correct code for this rule:

if (foo === null) {
  bar();
}

if (baz !== null) {
  bar();
}

if (bang === undefined) {
  bar();
}

How to use

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

CLI

oxlint --deny no-eq-null

Config (.oxlintrc.json)

{
  "rules": {
    "no-eq-null": "error"
  }
}

References

• Rule Source