diWiring checked by TypeScript

Define the capabilities your application needs, bind them at one edge, and compose modules whose missing dependencies are compile errors.

Ports belong to your application

Name a dependency for what your code needs, not for the database or service that provides it.

Missing wiring is a compile error

Providers declare their dependencies; modules declare what they export and expect from outside.

Internals stay private

A module exports selected ports while keeping its other providers unavailable to consumers.

Resources close with the scope

Module.scoped builds a graph, runs your work, and releases acquired resources on every exit path.

Use di on its own

@btravstack/di works without the btravstack application kernel or a server runtime. Install the container and its unthrown peer dependency:

pnpm add @btravstack/di unthrown

A port names a capability in your application's vocabulary. A provider constructs it, and a module chooses which ports the rest of the application can see. Module.scoped builds the graph, runs work with its typed context, and closes the scope.

The DI tutorial starts from an empty TypeScript project. For a larger application with production and in-memory adapters, see the hexagonal example. The complete exported surface is in the API reference.

Part ofBtravStack