harmony-collections 0.2.9

Provides Map, Set, and WeakMap with the same usage as the new ES6 native versions. Values in Harmony Collections are not contained in the collection instance itself, like array items and object properties, but in a private store. It's not possible to get access to or inspect the store directly.

harmony-collections@0.2.9 was published on 2012-06-25. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is 0.6.

All harmony-collections versions · Permanent reference to 0.2.9 · View npm registry JSON · Latest release

Package specifications

Version0.2.9
License declarationNot declared
Published2012-06-25T00:27:54.687Z
Node.js requirement0.6
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryharmony-collections.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository starsUnknown
Repository forksUnknown

Install harmony-collections 0.2.9

npm install harmony-collections@0.2.9
pnpm add harmony-collections@0.2.9
yarn add harmony-collections@0.2.9

Runtime dependencies

  • None declared

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