use-isnan should recommand using Number.isNaN

[DavidBruant]

isNaN is broken. ES6 fixed it with Number.isNaN which is easily polyfilled. Maybe the rule should recommend using Number.isNaN

[nzakas]

We can't assume someone is using a polyfill or ES6 at the moment, so we'd be giving advice that most people can't follow. Given that, I don't think this is actionable.

[DavidBruant]

The error message could recommend to use a polyfill for people to use.

[michaelficarra]

It could tell them to use x !== x, but that will trigger no-self-compare, which does not have the exception suggested in #374.

[ilyavolodin]

I honestly thing this is too situational to be a rule. In majority of the cases, isNaN works just fine, and suggesting to users to rely on third-party polyfill to do something that might works just fine for their use cases, feels like a wrong idea.

[nzakas]

When Number.isNaN() is more ubiquitous, I'm happy to revisit this decision.
At this time, I don't think making a change adds enough value.