useNumberNamespace

JavaScript (and super languages)

Summary

Rule available since: v1.5.0
Diagnostic Category: lint/style/useNumberNamespace
This rule has a safe fix.
The default severity of this rule is information.
Sources:
- Same as unicorn/prefer-number-properties

How to configure

1
{
2
  "linter": {
3
    "rules": {
4
      "style": {
5
        "useNumberNamespace": "error"
6
      }
7
    }
8
  }
9
}

Description

Use the Number properties instead of global ones.

ES2015 moved some globals into the Number properties for consistency.

The rule doesn’t report the globals isFinite and isNaN because they have a slightly different behavior to their corresponding Number’s properties Number.isFinite and Number.isNaN. You can use the dedicated rules noGlobalIsFinite and noGlobalIsNan to enforce the use of Number.isFinite and Number.isNaN.

Examples

Invalid

1
parseInt("1"); // true

code-block.js:1:1 lint/style/useNumberNamespace  FIXABLE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Use Number.parseInt instead of the equivalent global.
  
  > 1 │ parseInt(“1”); // true
      │ ^^^^^^^^
    2 │ 
  
  ℹ ES2015 moved some globals into the Number namespace for consistency.
  
  ℹ Safe fix: Use Number.parseInt instead.
  
    1   │ - parseInt(“1”);·//·true
      1 │ + Number.parseInt(“1”);·//·true
    2 2 │

1
parseFloat("1.1"); // true

code-block.js:1:1 lint/style/useNumberNamespace  FIXABLE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Use Number.parseFloat instead of the equivalent global.
  
  > 1 │ parseFloat(“1.1”); // true
      │ ^^^^^^^^^^
    2 │ 
  
  ℹ ES2015 moved some globals into the Number namespace for consistency.
  
  ℹ Safe fix: Use Number.parseFloat instead.
  
    1   │ - parseFloat(“1.1”);·//·true
      1 │ + Number.parseFloat(“1.1”);·//·true
    2 2 │

1
NaN; // true

code-block.js:1:1 lint/style/useNumberNamespace  FIXABLE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Use Number.NaN instead of the equivalent global.
  
  > 1 │ NaN; // true
      │ ^^^
    2 │ 
  
  ℹ ES2015 moved some globals into the Number namespace for consistency.
  
  ℹ Safe fix: Use Number.NaN instead.
  
    1   │ - NaN;·//·true
      1 │ + Number.NaN;·//·true
    2 2 │

1
Infinity; // true

code-block.js:1:1 lint/style/useNumberNamespace  FIXABLE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Use Number.POSITIVE_INFINITY instead of the equivalent global.
  
  > 1 │ Infinity; // true
      │ ^^^^^^^^
    2 │ 
  
  ℹ ES2015 moved some globals into the Number namespace for consistency.
  
  ℹ Safe fix: Use Number.POSITIVE_INFINITY instead.
  
    1   │ - Infinity;·//·true
      1 │ + Number.POSITIVE_INFINITY;·//·true
    2 2 │

1
-Infinity; // true

code-block.js:1:2 lint/style/useNumberNamespace  FIXABLE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Use Number.NEGATIVE_INFINITY instead of the equivalent global.
  
  > 1 │ -Infinity; // true
      │  ^^^^^^^^
    2 │ 
  
  ℹ ES2015 moved some globals into the Number namespace for consistency.
  
  ℹ Safe fix: Use Number.NEGATIVE_INFINITY instead.
  
    1   │ - -Infinity;·//·true
      1 │ + Number.NEGATIVE_INFINITY;·//·true
    2 2 │

Valid

1
Number.parseInt("1"); // false

1
Number.parseFloat("1.1"); // false

1
Number.NaN; // false

1
Number.POSITIVE_INFINITY; // false

1
Number.NEGATIVE_INFINITY; // false