CKTIS / JavaScript
Number.isFinite: a finite Number without coercion
Number.isFinite returns true only for a Number argument that is neither NaN nor positive or negative infinity.
Version: ECMAScript 2015 onward; example target: Node.js 24.22.2
Syntax
Number.isFinite(number)Number.isFinite(value) first checks the argument’s type. It returns true for every finite Number, including +0, -0, subnormal numbers, and Number.MAX_VALUE; it returns false for NaN, Infinity, and -Infinity. A missing argument is undefined and also produces false.
The method does not apply ToNumber. Strings, booleans, null, BigInt, Symbol, ordinary objects, and new Number(...) wrapper objects produce false, and their conversion hooks are not called. This differs from the global isFinite, which coerces: for example, isFinite("21.25") is true, while Number.isFinite("21.25") is false; the global form can also throw during conversion.
The method has existed since ECMAScript 2015 and is not a constructor. The example uses it at a temperature-validation boundary so that toFixed is called only on an actual finite Number. If numeric text is allowed as input, parse it explicitly and then check the result with Number.isFinite.
Examples
function formatTemperature(value) {
return Number.isFinite(value) ? `${value.toFixed(1)} C` : "invalid";
}
console.log([21.25, "21.25", NaN, Infinity].map(formatTemperature).join(" | "));
console.log(Number.isFinite(0), Number.isFinite(-0), Number.isFinite(Number.MAX_VALUE));
console.log(Number.isFinite(1n), Number.isFinite(Symbol("x")));
console.log(isFinite("21.25"), Number.isFinite("21.25"));Result
21.3 C | invalid | invalid | invalid true true true false false true false
Number.isFinite → strict temperature validation without coercion