@polkadot-api/merkleize-metadata 1.1.17

This TS package provides utils for the merkleization of [`frame_metadata`](https://docs.rs/frame-metadata/latest/frame_metadata/) as described in [RFC78](https://polkadot-fellows.github.io/RFCs/approved/0078-merkleized-metadata.html).

@polkadot-api/merkleize-metadata@1.1.17 was published on 2025-05-20. Its manifest declares 3 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.

All @polkadot-api/merkleize-metadata versions · Permanent reference to 1.1.17 · View npm registry JSON · Latest release

Package specifications

Version1.1.17
License declarationMIT
Published2025-05-20T12:40:07.262Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size536.98 KiB
Published file count24
Package typeNot declared
ES module entry./dist/esm/index.mjs
Default entry./dist/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies6
Repository stars157
Repository forks51

Install @polkadot-api/merkleize-metadata 1.1.17

npm install @polkadot-api/merkleize-metadata@1.1.17
pnpm add @polkadot-api/merkleize-metadata@1.1.17
yarn add @polkadot-api/merkleize-metadata@1.1.17

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