unicorn/prefer-array-some Pedantic

🛠️ An auto-fix is available for this rule.

What it does

Prefers using Array#some() over Array#find(), Array#findLast() with comparing to undefined, or Array#findIndex(), Array#findLastIndex() and a non-zero length check on the result of Array#filter()

Why is this bad?

Using .some() is more idiomatic and easier to read.

Examples

Examples of incorrect code for this rule:

const foo = array.find(fn) ? bar : baz;
const foo = array.findLast(elem => hasRole(elem)) !== null;
foo.findIndex(bar) < 0;
foo.findIndex(element => element.bar === 1) !== -1;
foo.findLastIndex(element => element.bar === 1) !== -1;
array.filter(fn).length === 0;

Examples of correct code for this rule:

const foo = array.some(fn) ? bar : baz;
foo.some(element => element.bar === 1);
!array.some(fn);

How to use

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

CLI

oxlint --deny unicorn/prefer-array-some

Config (.oxlintrc.json)

{
  "rules": {
    "unicorn/prefer-array-some": "error"
  }
}

References

• Rule Source