eslint/no-func-assign Correctness

✅ This rule is turned on by default.

What it does

Disallow reassigning function declarations

Why is this bad?

Overwriting/reassigning a function written as a FunctionDeclaration is often indicative of a mistake or issue.

Examples

Examples of incorrect code for this rule:

function foo() {}
foo = bar;

function foo() {
  foo = bar;
}

let a = function hello() {
  hello = 123;
};

Examples of correct code for this rule:

let foo = function() {};
foo = bar;

function baz(baz) { // `baz` is shadowed.
  baz = bar;
}

function qux() {
  const qux = bar;  // `qux` is shadowed.
}

How to use

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

CLI

oxlint --deny no-func-assign

Config (.oxlintrc.json)

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

References

• Rule Source