inversify-logging
Contextual logging for [inversify](https://github.com/inversify/InversifyJS) powered applications.
inversify-logging@0.2.1 was published on 2018-03-05. Its manifest declares 2 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All inversify-logging versions · Permanent reference to 0.2.1 · View npm registry JSON
Package specifications
| Version | 0.2.1 |
|---|---|
| License declaration | Not declared |
| Published | 2018-03-05T14:27:27.039Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 2 |
| Peer requirement count | 1 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 16.01 KiB |
| Published file count | 19 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | dist |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 2 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install inversify-logging 0.2.1
npm install inversify-logging@0.2.1 pnpm add inversify-logging@0.2.1 yarn add inversify-logging@0.2.1
Runtime dependencies
- lodash ^4.17.5
- reflect-metadata 0.1.8
Peer requirements
- inversify ^4.0.0
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- lodash@4.18.1 — direct
- reflect-metadata@0.1.8 — direct
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
- Readable npm registry JSON — retrieved 2026-11-04T15:23:55.129Z
- https://api.deps.dev/v3/systems/npm/packages/inversify-logging/versions/0.2.1 — retrieved 2026-11-04T15:23:55.380Z
- https://api.deps.dev/v3/systems/npm/packages/inversify-logging/versions/0.2.1:dependencies — retrieved 2026-11-04T15:23:55.398Z