Gathering detailed insights and metrics for is-number
Gathering detailed insights and metrics for is-number
Gathering detailed insights and metrics for is-number
Gathering detailed insights and metrics for is-number
is-number-object
Is this value a JS Number object? This module works cross-realm/iframe, and despite ES6 @@toStringTag.
number-is-nan
ES2015 `Number.isNaN()` ponyfill
is-natural-number
Check if a number is a natural number
is-negative-zero
Is this value negative zero? === will lie to you
JavaScript/Node.js utility. Returns `true` if the value is a number or string number. Useful for checking regex match results, user input, parsed strings, etc.
npm install is-number
Typescript
Module System
Min. Node Version
Node Version
NPM Version
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
277 Stars
62 Commits
51 Forks
9 Watchers
1 Branches
5 Contributors
Updated on Jun 30, 2025
Latest Version
7.0.0
Package Id
is-number@7.0.0
Size
3.64 kB
NPM Version
6.1.0
Node Version
10.0.0
Published on
Jul 04, 2018
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
4
Returns true if the value is a finite number.
Please consider following this project's author, Jon Schlinkert, and consider starring the project to show your :heart: and support.
Install with npm:
1$ npm install --save is-number
In JavaScript, it's not always as straightforward as it should be to reliably check if a value is a number. It's common for devs to use +
, -
, or Number()
to cast a string value to a number (for example, when values are returned from user input, regex matches, parsers, etc). But there are many non-intuitive edge cases that yield unexpected results:
1console.log(+[]); //=> 0 2console.log(+''); //=> 0 3console.log(+' '); //=> 0 4console.log(typeof NaN); //=> 'number'
This library offers a performant way to smooth out edge cases like these.
1const isNumber = require('is-number');
See the tests for more examples.
1isNumber(5e3); // true 2isNumber(0xff); // true 3isNumber(-1.1); // true 4isNumber(0); // true 5isNumber(1); // true 6isNumber(1.1); // true 7isNumber(10); // true 8isNumber(10.10); // true 9isNumber(100); // true 10isNumber('-1.1'); // true 11isNumber('0'); // true 12isNumber('012'); // true 13isNumber('0xff'); // true 14isNumber('1'); // true 15isNumber('1.1'); // true 16isNumber('10'); // true 17isNumber('10.10'); // true 18isNumber('100'); // true 19isNumber('5e3'); // true 20isNumber(parseInt('012')); // true 21isNumber(parseFloat('012')); // true
Everything else is false, as you would expect:
1isNumber(Infinity); // false 2isNumber(NaN); // false 3isNumber(null); // false 4isNumber(undefined); // false 5isNumber(''); // false 6isNumber(' '); // false 7isNumber('foo'); // false 8isNumber([1]); // false 9isNumber([]); // false 10isNumber(function () {}); // false 11isNumber({}); // false
.isFinite
if it exists.Breaking changes
instanceof Number
and instanceof String
As with all benchmarks, take these with a grain of salt. See the benchmarks for more detail.
# all
v7.0 x 413,222 ops/sec ±2.02% (86 runs sampled)
v6.0 x 111,061 ops/sec ±1.29% (85 runs sampled)
parseFloat x 317,596 ops/sec ±1.36% (86 runs sampled)
fastest is 'v7.0'
# string
v7.0 x 3,054,496 ops/sec ±1.05% (89 runs sampled)
v6.0 x 2,957,781 ops/sec ±0.98% (88 runs sampled)
parseFloat x 3,071,060 ops/sec ±1.13% (88 runs sampled)
fastest is 'parseFloat,v7.0'
# number
v7.0 x 3,146,895 ops/sec ±0.89% (89 runs sampled)
v6.0 x 3,214,038 ops/sec ±1.07% (89 runs sampled)
parseFloat x 3,077,588 ops/sec ±1.07% (87 runs sampled)
fastest is 'v6.0'
Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.
Running and reviewing unit tests is a great way to get familiarized with a library and its API. You can install dependencies and run tests with the following command:
1$ npm install && npm test
(This project's readme.md is generated by verb, please don't edit the readme directly. Any changes to the readme must be made in the .verb.md readme template.)
To generate the readme, run the following command:
1$ npm install -g verbose/verb#dev verb-generate-readme && verb
You might also be interested in these projects:
Object
constructor. | homepagetrue
if the value is a primitive. | homepageCommits | Contributor |
---|---|
49 | jonschlinkert |
5 | charlike-old |
1 | benaadams |
1 | realityking |
Jon Schlinkert
Copyright © 2018, Jon Schlinkert. Released under the MIT License.
This file was generated by verb-generate-readme, v0.6.0, on June 15, 2018.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
0 existing vulnerabilities detected
Reason
Found 3/24 approved changesets -- score normalized to 1
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More