inversify 6.1.4
A powerful and lightweight inversion of control container for JavaScript and Node.js apps powered by TypeScript.
inversify@6.1.4 was published on 2024-11-13. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All inversify versions · Permanent reference to 6.1.4 · View npm registry JSON · Latest release
Package specifications
| Version | 6.1.4 |
|---|---|
| License declaration | MIT |
| Published | 2024-11-13T20:08:34.243Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 1141.00 KiB |
| Published file count | 424 |
| Package type | Not declared |
| ES module entry | es/inversify.js |
| Default entry | lib/inversify.js |
| Side effects declaration | false |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 297 |
| Repository forks | 28 |
Install inversify 6.1.4
npm install inversify@6.1.4 pnpm add inversify@6.1.4 yarn add inversify@6.1.4
Runtime dependencies
- @inversifyjs/core 1.3.4
- @inversifyjs/common 1.3.3
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.
- @inversifyjs/common@1.3.3 — direct
- @inversifyjs/core@1.3.4 — direct
- @inversifyjs/reflect-metadata-utils@0.2.3 — indirect
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-03T09:05:08.614Z
- https://api.deps.dev/v3/systems/npm/packages/inversify/versions/6.1.4 — retrieved 2026-11-03T09:05:08.687Z
- https://api.deps.dev/v3/systems/npm/packages/inversify/versions/6.1.4:dependencies — retrieved 2026-11-03T09:05:08.713Z
- https://api.deps.dev/v3/projects/github.com%2Finversify%2Fmonorepo — retrieved 2026-11-03T07:05:49.316Z