New Rule: `no-new-bigint`

Rule details

Restricts calling BigInt with new like no-new-symbol

Related ECMAScript feature

BigInt

What type of rule is this?

Warns about a potential problem

Example code

// valid
const a = BigInt(9007199254740991);

// invalid
const b = new BigInt(9007199254740991);

Why should this rule be in the core instead of a plugin?

BigInt is a core feature of ECMAScript, also ESLint have no-new-symbol already.

Participation

• I am willing to submit a pull request to implement this rule.

Additional comments

No response

[mdjermanovic]

I’m not sure it’s valuable to start going down the path of creating a new rule for each function that looks like a constructor.

I agree. If we want to warn on new BigInt, then it might be better to add a rule that would warn on all ES globals that start with an uppercase letter but are not constructors (except those that are not functions, because they are included in no-obj-calls). It would include new Symbol, so the no-new-symbol rule would be deprecated.

[sosukesuzuki]

I prefer no-new-nonconstructor.