Registry / data / amp-is-number

amp-is-number

JSON →
library1.0.1jsnpmunverified

amp-is-number is a small, focused utility function originally developed as part of the Ampersand.js ecosystem. It provides a straightforward method to determine if a given JavaScript value is a number, including numeric strings, consistent with the logic prevalent in projects from the mid-2010s. Ampersand.js itself was a modular, Backbone.js-inspired framework, and `amp-is-number` was one of many atomic modules designed for composability. The package is at version 1.0.1, which appears to be its final release. There is no active development or release cadence for this specific utility, nor for the broader Ampersand.js project, which is considered abandoned. This package exclusively uses CommonJS module syntax, reflecting the standard module patterns of its era, and it lacks explicit support for modern ECMAScript modules (ESM). It differs from more recent `is-number` implementations by not necessarily incorporating newer JavaScript language features or edge case handling, instead focusing on the behavior expected within its original framework context.

data
npm install amp-is-number
github ↗package ↗homepage ↗
INSTALL
IMPORT
SIG · AMP-IS-NUMBER
A
amp-is-number
datajavascriptv1.0.1
Install
—
Import
—
Disk
—
Pass rate
0/ 6
Env Coverage0 / 6
glibc
18–22
musl
18–22
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18–226 runs
build_error
glibc
node 18–226 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

isNumber
✓ const isNumber = require('amp-is-number');
✗ import { isNumber } from 'amp-is-number';
This package is CommonJS-only. Direct ESM imports like `import ... from 'amp-is-number'` will fail in native ESM environments. Use `require()` or dynamic `import()` for ESM interoperability.
isNumber (dynamic import)
✓ const isNumber = await import('amp-is-number'); const result = isNumber.default(123);
When using dynamic import() in an ESM context, CommonJS modules are imported as a module namespace object, where the default export is the `module.exports` value.

Demonstrates how to import and use the `isNumber` function to check various data types.

const isNumber = require('amp-is-number'); console.log('Is 123 a number?', isNumber(123)); // Expected: true console.log('Is "456" a number?', isNumber('456')); // Expected: true console.log('Is "hello" a number?', isNumber('hello')); // Expected: false console.log('Is null a number?', isNumber(null)); // Expected: false console.log('Is undefined a number?', isNumber(undefined)); // Expected: false console.log('Is NaN a number?', isNumber(NaN)); // Expected: false // Example of usage in a conditional function processValue(value) { if (isNumber(value)) { console.log(`Processing number: ${Number(value)}`); } else { console.log(`Value is not a recognized number: ${value}`); } } processValue('99.5'); processValue({});
Debug
Known issues
breakingThis package is CommonJS-only (uses `module.exports`). It does not provide an ESM export and will cause a `TypeError: require is not a function` error if directly imported in a pure ES Module environment without a CommonJS wrapper or bundler transpilation.
fix
For ESM environments, use `const isNumber = await import('amp-is-number');` and access the function via `isNumber.default()`, or configure your build system (e.g., Webpack, Rollup) to handle CommonJS modules.
affects: 1.0.1
gotchaThe Ampersand.js project, including `amp-is-number`, is no longer actively maintained. Expect no further updates, bug fixes, or security patches. While simple, its implementation might not cover modern JavaScript edge cases or optimizations found in newer utility libraries.
fix
For new projects, consider using native `Number.isFinite()` or a more modern, actively maintained `is-number` utility package if its specific string-to-number coercion behavior is not strictly required. For existing projects, be aware of its unmaintained status.
affects: 1.0.1
gotchaThe logic for determining a 'number' might differ subtly from `Number.isFinite()` or other popular `is-number` libraries, especially regarding whitespace-only strings, `null`, or `NaN`. It was designed for the Ampersand.js ecosystem's specific needs.
fix
Review the source code of `amp-is-number` if precise behavior for edge cases is critical for your application to ensure it aligns with expectations. Consider migrating to `Number.isFinite()` or a modern alternative if a more standard or robust number check is needed.
affects: 1.0.1
Errors
Common errors & fixes
TypeError: require is not a function
Attempting to use `require()` in an ECMAScript Module (ESM) file, or importing a CommonJS module (like `amp-is-number`) directly with `import` in a native ESM environment without proper interoperability handling.
fix
If in an ESM file, use `await import('amp-is-number')` and access the default export: `(await import('amp-is-number')).default(value)`. Alternatively, switch your file to CommonJS if possible, or ensure your build tools are correctly transpiling.
Upgrade
Version history
1.0.1latest on npm
Audit
Dependencies

No dependency data recorded yet.

Agent activity
38 hits · last 30 days
node
30
OpenAI (training)
1
Resources
githubhttps://github.com/ampersandjs/amp ↗
packagehttps://www.npmjs.com/package/amp-is-number ↗
homepagehttp://amp.ampersandjs.com/#amp-is-number ↗
amp-is-number — npm install amp-is-number · libregistry