pm2-rpc-fallback

PM2 upgrade procedures

pm2-rpc-fallback@3.0.9 was published on 2014-10-11. Its manifest declares 6 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 pm2-rpc-fallback versions · Permanent reference to 3.0.9

Package specifications

Version3.0.9
License declarationNot declared
Published2014-10-11T13:19:52.036Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count6
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 entryindex
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies14
Repository starsUnknown
Repository forksUnknown

Install pm2-rpc-fallback 3.0.9

npm install pm2-rpc-fallback@3.0.9
pnpm add pm2-rpc-fallback@3.0.9
yarn add pm2-rpc-fallback@3.0.9

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