Core model

Wyrly has a small core model. Most applications only need five ideas: tokens, providers, containers, scopes, and lifetimes.

Tokens

A token is a runtime key with a TypeScript type.

const UserRepositoryToken = token<UserRepository>("UserRepository");

Use tokens for interfaces and abstract capabilities. Class constructors can also be registered directly when the class itself is the dependency key.

A provider tells the container how to create or return a dependency. Wyrly supports:

The root container owns application-wide registrations.

const container = createContainer();
container.register(UserRepositoryToken, {
  useClass: PrismaUserRepository,
  lifetime: "scoped",
});

Treat the root container as the composition root. Register concrete infrastructure there rather than inside domain or use case code.

A scope is a child resolution context. In web apps, adapters usually create one scope per request.

const scope = container.createScope();
try {
  const service = scope.resolve(MyService);
} finally {
  await scope.dispose();
}

Scoped dependencies are reused within the same scope and disposed when the scope is disposed.

Lifetime	Meaning
`singleton`	one instance for the root container
`scoped`	one instance per scope
`transient`	a new instance on each resolution

Pick the narrowest lifetime that matches the dependency’s state and resource ownership.

Use container.validate() to catch graph problems before production:

Validation is especially useful in CI because it turns dependency wiring into a checkable artifact.