Comparing version 1.3.2 to 1.3.3
{ | ||
"name": "types.js", | ||
"version": "1.3.2", | ||
"version": "1.3.3", | ||
"description": "A tiny (1.7kb), but essential Javascript type-check library", | ||
@@ -5,0 +5,0 @@ "main": "types.min.js", |
@@ -10,6 +10,2 @@ types.js | ||
Standard Javascript `(NaN == NaN) == false` still freakes me out, it's so wrong..<br/> | ||
You cannot add to `NaN`, that's logical. But if `(typof NaN == 'number')` how can we know if our value is a number?<br/> | ||
Well: `(value == value)`, because `(NaN != NaN)`, omg! I refuse to have this in my code, except for this library! | ||
With types.js: | ||
@@ -34,2 +30,3 @@ ```javascript | ||
} | ||
// check if parseInt returned NaN.. | ||
if ( left !== left || typeof left !== 'number' ) | ||
@@ -36,0 +33,0 @@ left= 100; |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
12
141519
235