unicorn/prefer-number-properties Restriction

🚧 An auto-fix is still under development.

What it does

Disallows use of parseInt(), parseFloat(), isNan(), isFinite(), Nan, Infinity and -Infinity as global variables.

Why is this bad?

ECMAScript 2015 moved globals onto the Number constructor for consistency and to slightly improve them. This rule enforces their usage to limit the usage of globals:

• Number.parseInt() over parseInt()
• Number.parseFloat() over parseFloat()
• Number.isNaN() over isNaN() (they have slightly different behavior)
• Number.isFinite() over isFinite() (they have slightly different behavior)
• Number.NaN over NaN
• Number.POSITIVE_INFINITY over Infinity
• Number.NEGATIVE_INFINITY over -Infinity

Examples

Examples of incorrect code for this rule:

const foo = parseInt("10", 2);
const bar = parseFloat("10.5");

Examples of correct code for this rule:

const foo = Number.parseInt("10", 2);
const bar = Number.parseFloat("10.5");

References

• Rule Source