@microsoft/package-deps-hash 2.3.1

The `package-deps-hash` library generates a JSON object containing the git hashes of all files used to produce a given package. This is useful for scenarios where you want to define a "change receipt" file to be published with a package. The [Rush](ht

@microsoft/package-deps-hash@2.3.1 was published on 2019-10-10. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @microsoft/package-deps-hash versions · Permanent reference to 2.3.1 · Latest release

Package specifications

Version2.3.1
License declarationMIT
Published2019-10-10T23:29:51.570Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size138.05 KiB
Published file count19
Package typeNot declared
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies13
Repository starsUnknown
Repository forksUnknown

Install @microsoft/package-deps-hash 2.3.1

npm install @microsoft/package-deps-hash@2.3.1
pnpm add @microsoft/package-deps-hash@2.3.1
yarn add @microsoft/package-deps-hash@2.3.1

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