← Back to rules

eslint/no-obj-calls Correctness

✅ This rule is turned on by default.

What it does

Disallow calling some global objects as functions.

This rule can be disabled for TypeScript code, as the TypeScript compiler enforces this check.

Why is this bad?

Some global objects are not intended to be called as functions. Calling them as functions will usually result in a TypeError being thrown.

Examples

Examples of incorrect code for this rule:

let math = Math();
let newMath = new Math();

let json = JSON();
let newJson = new JSON();

let atomics = Atomics();
let newAtomics = new Atomics();

let intl = Intl();
let newIntl = new Intl();

let reflect = Reflect();
let newReflect = new Reflect();

Examples of correct code for this rule:

let area = (r) => 2 * Math.PI * r * r;
let object = JSON.parse("{}");
let first = Atomics.load(sharedArray, 0);
let segmenterFrom = Intl.Segmenter("fr", { granularity: "word" });

How to use

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

Config (.oxlintrc.json)

{
  "rules": {
    "no-obj-calls": "error"
  }
}

Config (oxlint.config.ts)

import { defineConfig } from "oxlint";

export default defineConfig({
  rules: {
    "no-obj-calls": "error",
  },
});

CLI

oxlint --deny no-obj-calls

Version

This rule was added in v0.0.7.

References

• Rule Source
• Upstream rule docs
• Open rule in Oxc Playground