no-new-object

Disallow Object constructors

This rule was deprecated in ESLint v8.50.0 and replaced by the no-object-constructor rule. The new rule flags more situations where object literal syntax can be used, and it does not report a problem when the Object constructor is invoked with an argument.

The Object constructor is used to create new generic objects in JavaScript, such as:

var myObject = new Object();
1

However, this is no different from using the more concise object literal syntax:

var myObject = {};
1

For this reason, many prefer to always use the object literal syntax and never use the Object constructor.

While there are no performance differences between the two approaches, the byte savings and conciseness of the object literal form is what has made it the de facto way of creating new objects.

Rule Details

This rule disallows calling the Object constructor with new.

Examples of incorrect code for this rule:

/*eslint no-new-object: "error"*/

var myObject = new Object();

new Object();

var foo = new Object("foo");
1
2
3
4
5
6
7

Examples of correct code for this rule:

/*eslint no-new-object: "error"*/

var myObject = new CustomObject();

var myObject = {};

var Object = function Object() {};
new Object();

var foo = Object("foo");
1
2
3
4
5
6
7
8
9
10

When Not To Use It

If you wish to allow the use of the Object constructor with new, you can safely turn this rule off.

Related Rules

• no-array-constructor
• no-new-wrappers

Version

This rule was introduced in ESLint v0.0.9.

Resources

• Rule source
• Tests source