hexagonal-inversify-di

Wire Hexagonal architecture ports and adapters with InversifyJS by creating core-*, driven-*, and driving-* packages, defining dual identifier ports, implementing adapters, and composing app containers with explicit binding order per runtime. This enforces consistent container wiring and prevents adapter-to-adapter coupling.

The dual identifier port pattern in TypeScript dependency injection pairs an interface with a Symbol to make ports injectable and type-safe. This ensures tokens are uniquely identified within the InversifyJS container and prevents multi-token aliasing issues during binding.

Set up InversifyJS composition roots for browser extension runtimes by creating separate bootstrap containers per runtime, such as for MV2 and MV3. Never share containers across extension runtimes to avoid state conflicts and unexpected container initialization behavior.

InversifyJS enforces default singleton scope for use cases in Hexagonal architecture by utilizing createCore<Name>Container factory conventions. This ensures consistent application state management and prevents accidental transient bindings when composing app containers.

InversifyJS container binding fails when using Symbol instead of Symbol.for because Symbol generates unique instances across modules, breaking identifier matching. Use Symbol.for to ensure global symbol registry sharing for your ports and adapters.

The required binding order for InversifyJS adapter setupContainer static registration dictates calling createCore<Name>Container first, followed by registering driven and driving adapters. This explicit composition root order ensures dependencies are available before adapter resolution.