lock-me

Lock files across processes

lock-me@1.0.4 was published on 2018-05-22. Its manifest declares 5 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All lock-me versions · Permanent reference to 1.0.4

Package specifications

Version1.0.4
License declarationMIT
Published2018-05-22T10:46:47.571Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count5
Peer requirement count0
Optional dependency count1
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size574.11 KiB
Published file count14
Package typeNot declared
ES module entryNot declared
Default entrysrc/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies16
Repository starsUnknown
Repository forksUnknown

Install lock-me 1.0.4

npm install lock-me@1.0.4
pnpm add lock-me@1.0.4
yarn add lock-me@1.0.4

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • fs-ext github:baudehlo/node-fs-ext#master

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