no-array-constructor

Disallow Array constructors

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.

Rule Details

This rule disallows Array constructors.

Examples of incorrect code for this rule:

/*eslint no-array-constructor: "error"*/ Array(); Array(0, 1, 2); new Array(0, 1, 2); Array(...args); 
1
2
3
4
5
6
7
8
9

Examples of correct code for this rule:

/*eslint no-array-constructor: "error"*/ Array(500); new Array(someOtherArray.length); [0, 1, 2]; const createArray = Array => new Array(); 
1
2
3
4
5
6
7
8
9

This rule additionally supports TypeScript type syntax.

Examples of correct code for this rule:

/*eslint no-array-constructor: "error"*/ new Array<number>(1, 2, 3); new Array<Foo>(); Array<number>(1, 2, 3); Array<Foo>(); Array?.foo(); 
1
2
3
4
5
6
7
8
9
10
11

Examples of incorrect code for this rule:

/*eslint no-array-constructor: "error"*/ new Array(); new Array(0, 1, 2); Array?.(x, y); Array?.(0, 1, 2); 
1
2
3
4
5
6
7
8
9

When Not To Use It

This rule enforces a nearly universal stylistic concern. That being said, this rule may be disabled if the constructor style is preferred.

Related Rules

• no-new-wrappers
• no-object-constructor

Version

This rule was introduced in ESLint v0.4.0.

Resources

• Rule source
• Tests source