docs/src/rules/no-array-constructor.md
Use of the Array constructor to construct a new array is generally
discouraged in favor of array literal notation because of the single-argument
pitfall and because the Array global may be redefined. The exception is when
the Array constructor is used to intentionally create sparse arrays of a
specified size by giving the constructor a single numeric argument.
This rule disallows Array constructors.
Examples of incorrect code for this rule:
:::incorrect
/*eslint no-array-constructor: "error"*/
Array();
Array(0, 1, 2);
new Array(0, 1, 2);
Array(...args);
:::
Examples of correct code for this rule:
:::correct
/*eslint no-array-constructor: "error"*/
Array(500);
new Array(someOtherArray.length);
[0, 1, 2];
const createArray = Array => new Array();
:::
This rule additionally supports TypeScript type syntax.
Examples of correct code for this rule:
:::correct
/*eslint no-array-constructor: "error"*/
new Array<number>(1, 2, 3);
new Array<Foo>();
Array<number>(1, 2, 3);
Array<Foo>();
Array?.foo();
:::
Examples of incorrect code for this rule:
:::incorrect
/*eslint no-array-constructor: "error"*/
new Array();
new Array(0, 1, 2);
Array?.(x, y);
Array?.(0, 1, 2);
:::
This rule has no options.
This rule enforces a nearly universal stylistic concern. That being said, this rule may be disabled if the constructor style is preferred.