News for hackers. Stuff that matters.

A comment on NPM Vulnerability Discussion on Twitter. Parent comment

Re:NPM Vulnerability Discussion on Twitter by jefftk on Tuesday May 10, 2022 @11:03AM (#31327967)
Regular isNaN is very tricky, and almost never what you want: it first coerces its input to a Number, and then checks if that is NaN:

                isNaN   Number.isNaN
                -----   ------------
    {}           true          false
    [true]       true          false
    undefined    true          false
    "{}"         true          false
[ Parent | on HN ]
Re:NPM Vulnerability Discussion on Twitter by jaywalk on Tuesday May 10, 2022 @11:50AM (#31328546)
But none of those things you listed are numbers. The isNaN output is exactly what I want in pretty much every case.
[ Parent | on HN ]
Re:NPM Vulnerability Discussion on Twitter by jefftk on Tuesday May 10, 2022 @11:55AM (#31328620)
isNaN does not tell you whether something is not a Number either. Applying isNaN to any of these returns false: null, true, false, [], "", "cabbage".
[ Parent | on HN ]