@stdlib/number-float32-base-assert-is-almost-equal 0.1.0

Test if two single-precision floating-point numbers are approximately equal within a specified number of ULPs (units in the last place).

@stdlib/number-float32-base-assert-is-almost-equal@0.1.0 was published on 2026-01-30. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=0.10.0.

All @stdlib/number-float32-base-assert-is-almost-equal versions · Permanent reference to 0.1.0 · Latest release

Package specifications

Version0.1.0
License declarationApache-2.0
Published2026-01-30T20:07:53.663Z
Node.js requirement>=0.10.0
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size28.86 KiB
Published file count11
Package typeNot declared
ES module entryNot declared
Default entry./lib
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies10
Repository stars0
Repository forks0

Install @stdlib/number-float32-base-assert-is-almost-equal 0.1.0

npm install @stdlib/number-float32-base-assert-is-almost-equal@0.1.0
pnpm add @stdlib/number-float32-base-assert-is-almost-equal@0.1.0
yarn add @stdlib/number-float32-base-assert-is-almost-equal@0.1.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

Evidence and freshness