Skip to main content

javascript math.isnan

 Number.isNaN() is a method used to determine whether a value is NaN (Not-a-Number) and is of type number. 

It is different from the global isNaN() function in that it does not coerce the value to a number before testing it. 

This means that Number.isNaN() is a more reliable way to test specifically for NaN values.

Syntax


Number.isNaN(value)
  • value: The value to test.

Returns

  • true if the value is NaN and is of type number.
  • false otherwise.

Differences from isNaN()

  • Number.isNaN() checks if a value is exactly NaN.
  • isNaN() coerces the value to a number before checking, which can lead to unexpected results.

Examples

Here are 10 examples demonstrating how Number.isNaN() works:

  1. Basic NaN Check


    console.log(Number.isNaN(NaN)); // true
  2. Number that is not NaN


    console.log(Number.isNaN(123)); // false
  3. String that is not NaN


    console.log(Number.isNaN('hello')); // false
  4. Number object with NaN value


    let numObj = new Number(NaN); console.log(Number.isNaN(numObj)); // false
  5. Infinity (Positive)


    console.log(Number.isNaN(Infinity)); // false
  6. Infinity (Negative)


    console.log(Number.isNaN(-Infinity)); // false
  7. NaN from arithmetic operation


    let result = 0 / 0; console.log(Number.isNaN(result)); // true
  8. Boolean value


    console.log(Number.isNaN(true)); // false console.log(Number.isNaN(false)); // false
  9. Null value


    console.log(Number.isNaN(null)); // false
  10. Array containing NaN


    let array = [NaN]; console.log(Number.isNaN(array[0])); // true

Key Points

  • NaN is a special value in JavaScript that stands for "Not-a-Number" and is a member of the number type.
  • Number.isNaN() is more precise for checking NaN values compared to the global isNaN(), which can produce unexpected results due to type coercion.

Popular posts from this blog

How to Set Up a Linux Web Server and Host an HTML Page Easily

Setting up a web server on Linux means spending a fair amount of time in the terminal — Linux leans heavily on the command line rather than clicking through menus, so you'll be typing out instructions more often than not.  If you're new to this, it can feel a little intimidating at first, but the good news is you don't need to become a Linux wizard overnight. A handful of core commands will get you surprisingly far. A few you'll lean on constantly: cd — move between directories ls — see what's in the current directory mkdir — create a new folder nano or vim — edit files right there in the terminal sudo — run something with administrator privileges Get comfortable with these and you'll be able to navigate around, tweak configuration files, and install software without much trouble. You don't need to memorize everything — you just need to be confident enough to follow along with clear instructions, which is exactly what this guide aims to give you....

How to Check if Someone is Connected to Your Machine in Linux

Picture this: you glance at your system monitor and notice your CPU is humming along even though you're not running anything demanding. Or maybe your internet feels sluggish for no obvious reason. A small, uneasy thought creeps in — is someone else on my machine right now? For Linux users, this isn't something you have to wonder about. Linux ships with a powerful set of built-in tools that let you see exactly who's connected, who's logged in, and what your network is doing at any given moment. You don't need to be a security expert to use them — you just need to know where to look. This guide walks you through the practical, no-nonsense steps to check for unauthorized connections on your Linux system, with real commands you can run right now. Why Monitoring Network Connections Matters Every device on a network — including your own Linux machine — communicates using an IP address. When another device or user connects to your system, that connection shows up as a trac...

Linux Network Troubleshooting

If you've spent any time as a sysadmin — or honestly, just as someone who's had to fix their own home network at 11pm — you know that connectivity issues are one of the most common headaches out there. The good news is that a handful of core tools and a methodical approach can take you from "why isn't this working" to a root cause pretty quickly.  This guide walks through the essentials: configuring interfaces, managing routes, and diagnosing problems when things go sideways. Configuring Network Interfaces Your network interfaces are the actual bridge between your machine and the outside world, so getting them configured correctly is step one for any kind of reliable connectivity. Doing It Manually ifconfig is the old-school, tried-and-true tool for this on Unix-like systems. To see everything currently configured, run: ifconfig -a If you need to manually set up a specific interface — assigning an IP, a netmask, and bringing it online — it looks like this: ifconf...