unicorn/prefer-dom-node-text-content Style

What it does

Enforces the use of .textContent over .innerText for DOM nodes.

Why is this bad?

There are some disadvantages of using .innerText.

• .innerText is much more performance-heavy as it requires layout information to return the result.
• .innerText is defined only for HTMLElement objects, while .textContent is defined for all Node objects.
• .innerText is not standard, for example, it is not present in Firefox.

Examples

Examples of incorrect code for this rule:

const text = foo.innerText;

Examples of correct code for this rule:

const text = foo.textContent;

How to use

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

Config (.oxlintrc.json)

{
  "rules": {
    "unicorn/prefer-dom-node-text-content": "error"
  }
}

CLI

oxlint --deny unicorn/prefer-dom-node-text-content

References

• Rule Source