Scopes and Teardown

A scope bounds the lifetime of request-local services to a single unit of work. A child scope inherits every parent registration, but caches its own scoped instances and owns their teardown — so the scope created for one request never shares state with, or outlives, another.

const root = new Container()
  .registerClass('db', Db, [])
  .registerClass('request', RequestContext, [], 'scoped')

async function handle(request: Request) {
  await using scope = root.createScope()
  const ctx = scope.get('request')
}

db is a root singleton. request is created once per scope and disposed when the scope is disposed.

Ownership

Each container disposes only instances it created.

Instance	Owner
Root singleton	Root container
Scoped service	Request scope
Singleton first resolved on a child	That child container
Transient	Caller

root.dispose() does not cascade into already-created child scopes. Dispose scopes at their own lifecycle boundary.

Native Resource Management

Container implements both disposal symbols:

using syncScope = root.createScope()
await using asyncScope = root.createScope()

Use await using or await container.dispose() when any owned resource may be async.

Disposal Protocol

Owned instances are disposed in reverse creation order. The container probes:

1. Symbol.asyncDispose
2. Symbol.dispose
3. .dispose()

If multiple disposers fail, InferDI collects them in an AggregateError so one bad cleanup does not prevent later resources from closing.