Monorepo consolidating three package families under one workspace:

• di — type-driven, interface-first dependency injection for TypeScript
• config — layered, provider-based configuration for TypeScript
• hosting — (skeletons pending)

Flat, not nested by family:

• libraries/<name-without-scope> — one directory per published package, e.g. libraries/core, libraries/config-json.
• examples/examples.<kind>.<name> — the interop-matrix example set: two dependency libraries (examples.lib.with-transformer / .without-transformer), two composition-root apps (examples.app.with-transformer / .without-transformer) running one integrated scenario each, and the type-only examples.contracts they share. Each dialect both produces and consumes the other.

Packages are bun workspaces and consume each other's raw TypeScript source directly (no build step between them) via workspace:* dependencies and moduleResolution: "bundler" in tsconfig.base.json.

• bun workspaces with the isolated linker (bunfig.toml: [install] linker = "isolated") — no flattened node_modules, no linkWorkspacePackages.
• dprint for formatting, eslint (typescript-eslint) for linting, tsc -b for typechecking against the empty root solution stub.

Some packages (the di and config transformers, and anything that consumes them) rely on a custom TypeScript transformer applied at compile time. Those packages build with tspc (from ts-patch), not plain tsc — wire this up per-package via a plugins entry in that package's tsconfig.json plus an import of the transformer package in the consuming entry point. ts-patch and rollup/rollup-plugin-dts live at the monorepo root so every workspace can reach them.

This is root scaffolding only — no package sources have been imported yet. Releases and CI are intentionally not configured.