eslint/no-ex-assign Correctness

✅ This rule is turned on by default.

What it does

Disallow reassigning exceptions in catch clauses

Why is this bad?

If a catch clause in a try statement accidentally (or purposely) assigns another value to the exception parameter, it is impossible to refer to the error from that point on. Since there is no arguments object to offer alternative access to this data, assignment of the parameter is absolutely destructive.

Example

try {
  // code
} catch (e) {
  e = 10;
}

How to use

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

CLI

oxlint --deny no-ex-assign

Config (.oxlintrc.json)

{
  "rules": {
    "no-ex-assign": "error"
  }
}

References

• Rule Source