@financial-times/polyfill-useragent-normaliser 1.10.2

The user-agent normalisation logic behind polyfill-library and polyfill.io

@financial-times/polyfill-useragent-normaliser@1.10.2 was published on 2022-04-05. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=8.

Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

All @financial-times/polyfill-useragent-normaliser versions · Permanent reference to 1.10.2 · Latest release

Package specifications

Version1.10.2
License declarationMIT
Published2022-04-05T17:10:54.429Z
Node.js requirement>=8
Type declarationsNot declared
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size366.13 KiB
Published file count30
Package typeNot declared
ES module entryNot declared
Default entrylib/normalise-user-agent.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies2
Repository stars22
Repository forks9

Install @financial-times/polyfill-useragent-normaliser 1.10.2

npm install @financial-times/polyfill-useragent-normaliser@1.10.2
pnpm add @financial-times/polyfill-useragent-normaliser@1.10.2
yarn add @financial-times/polyfill-useragent-normaliser@1.10.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.

Evidence and freshness