ioc-manifestTyped IoC for Awilix, by convention

Write factory functions or classes, run the generator, get a fully typed container — no manual registrations. First-class monorepo composition.

How it fits together

Quick start

GitHub

Factories or classes

Export buildUserService, or write class UserService implements UserContract. Either is a registration unit; both get the same key, and they mix freely.

Contracts you declared

A unit's contract is the name you wrote at its contract site — a return annotation or an implements clause — read syntactically. No central registry, no inference from checker normalization.

Typed end-to-end

container.resolve("userService") returns UserService, not any — a fully typed IocGeneratedCradle generated from your source.

Type-safe groups

Declare a collection or object group over a base type and resolve every implementation as a typed array or keyed object — discovered automatically, composed across packages.

Cross-package composition

Apps in a monorepo compose manifests from multiple packages with no scanning across boundaries, and compile-time externals checks.

Lifetime-inversion safety

Generation fails when a longer-lived service would freeze a shorter-lived dependency — catching a class of stale-state bugs statically.

No runtime scanning

The generated manifest is plain TypeScript with static imports. Output is ordinary Awilix — zero lock-in, works in dev and bundled prod.