objectCalls

Prefer {} object literal notation or Object.create instead of calling or constructing Object.

✅ This rule is included in the ts stylistic and stylisticStrict presets.

Calling or constructing the global Object directly is unnecessarily verbose and less idiomatic than using object literal syntax. Object literal notation {} is the preferred and more concise way to create plain objects in JavaScript and TypeScript.

const 
const emptyObject: Object
emptyObject = new 
var Object: ObjectConstructor
new (value?: any) => Object
Provides functionality common to all JavaScript objects.
Object();

const 
const emptyObject: any
emptyObject = 
var Object: ObjectConstructor
() => any (+1 overload)
Object();

const 
const config: Object
config = new 
var Object: ObjectConstructor
new (value?: any) => Object
Provides functionality common to all JavaScript objects.
Object({ 
key: string
key: "value" });

const 
const config: any
config = 
var Object: ObjectConstructor
(value: any) => any (+1 overload)
Object({ 
key: string
key: "value" });

const 
const emptyObject: {}
emptyObject = {};

const 
const config: {
    key: string;
}
config = { 
key: string
key: "value" };

const 
const objectWithoutPrototype: any
objectWithoutPrototype = 
var Object: ObjectConstructor
Provides functionality common to all JavaScript objects.
Object.
ObjectConstructor.create(o: object | null): any (+1 overload)
Creates an object that has the specified prototype or that has null prototype.
@param ― o Object to use as a prototype. May be null.
create(null);

const 
const copy: any
copy = 
var Object: ObjectConstructor
Provides functionality common to all JavaScript objects.
Object.
ObjectConstructor.assign<{}, any>(target: {}, source: any): any (+3 overloads)
Copy the values of all of the enumerable own properties from one or more source objects to a
target object. Returns the target object.
@param ― target The target object to copy to.
@param ― source The source object from which to copy properties.
assign({}, 
const source: any
source);

Options

This rule is not configurable.

When Not To Use It

If you have an existing codebase style that would be difficult to migrate away from, such as for consistency preferences with legacy code, you might find it difficult to onboard to this rule. Alternately, if you target a legacy runtime with behavioral quirks where object literals behave differently than Object() calls, this rule might be counterproductive for you.

Equivalents in Other Linters

ESLint: no-object-constructor
Oxlint: eslint/no-object-constructor

Made with ❤️‍🔥 around the world by the Flint team and contributors.

objectCalls

Examples

Options

When Not To Use It

Further Reading

Equivalents in Other Linters