melody-extension-core 1.2.0-commit.e09ceb68

melody-extension-core@1.2.0-commit.e09ceb68 was published on 2018-09-17. Its manifest declares 4 runtime dependencies and 5 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All melody-extension-core versions · Permanent reference to 1.2.0-commit.e09ceb68 · Latest release

Package specifications

Version1.2.0-commit.e09ceb68
License declarationApache-2.0
Published2018-09-17T15:14:32.672Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count4
Peer requirement count5
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size243.38 KiB
Published file count32
Package typeNot declared
ES module entryNot declared
Default entry./lib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository starsUnknown
Repository forksUnknown

Install melody-extension-core 1.2.0-commit.e09ceb68

npm install melody-extension-core@1.2.0-commit.e09ceb68
pnpm add melody-extension-core@1.2.0-commit.e09ceb68
yarn add melody-extension-core@1.2.0-commit.e09ceb68

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

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