npm upgrade
Homeinversify 6 → 7
6.2.2 → 7.11.0. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
inversify 7.11.0 removes or renames exports your code may import.
- Removed
- 16
- Renamed
- 0
- Signature changes
- 0
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 4
Does this break your code?
Run this in your project. It compares both releases against the names your code actually imports, locally, with no account and nothing sent to lurq:
npx lurqrun check-upgrade --upgrade inversify@6.2.2..7.11.0
To have your coding agent check upgrades like this before it writes them, connect lurq to Claude Code, Cursor, VS Code or Codex:
npx lurqrun
Removed
Gone at runtime, with no replacement found under another name. Imports of these fail.
- AsyncContainerModuleobject
- BindingScopeEnumobject
- BindingTypeEnumobject
- LazyServiceIdentiferobject
- METADATA_KEYobject
- MetadataReaderobject
- TargetTypeEnumobject
- createTaggedDecoratorobject
- getServiceIdentifierAsStringobject
- idobject
- multiBindToServiceobject
- namedConstraintobject
- taggedConstraintobject
- targetNameobject
- traverseAncerstorsobject
- typeConstraintobject
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Oct 11, 2026. inversify on lurq.