@formatjs/intl-utils 0.4.2

Smartly determine best unit for relative time format

@formatjs/intl-utils@0.4.2 was published on 2019-07-23. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: the package is rather renamed to @formatjs/ecma-abstract with some changes in functionality (primarily selectUnit is removed and we don't plan to make any further changes to this package

All @formatjs/intl-utils versions · Permanent reference to 0.4.2 · Latest release

Package specifications

Version0.4.2
License declarationMIT
Published2019-07-23T14:44:15.311Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size11.43 KiB
Published file count14
Package typeNot declared
ES module entrylib/index.js
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies3
Repository stars14751
Repository forks1387

Install @formatjs/intl-utils 0.4.2

npm install @formatjs/intl-utils@0.4.2
pnpm add @formatjs/intl-utils@0.4.2
yarn add @formatjs/intl-utils@0.4.2

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.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review0/10 — Found 2/30 approved changesets -- score normalized to 0
Maintained10/10 — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
License0/10 — license file not detected
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Fuzzing0/10 — project is not fuzzed
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
Security-Policy0/10 — security policy file not detected
Packaging10/10 — packaging workflow detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness