packages/typert
September 4, 2026 · View on GitHub
English | 中文
Summary
With the typert group, Client environments can call Host capabilities as typed methods and share generated schemas and reflection without hand-written wire code. A build-time generator turns source type declarations into compiler-independent models and runtime artifacts, a runtime registry stores those artifacts, and a Loader integration registers them automatically in Loader compositions. A shared protocol package supplies the Remote-call declarations — decorators, wire descriptors, codecs, and provider contracts — that business packages, generated artifacts, the Host Gateway, and the Client API all consume. This page maps the four packages; each package README owns its configuration, usage, and limits.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
generator/ | Analyzes source types at build time and generates the reflection, schemas, and Remote descriptors that runtimes load | — |
loader/ | Auto-registers generated Typert artifacts from Loader compositions into the runtime registry | consumes ctx.loader and ctx.typert |
protocol/ | Declares the Remote decorators, wire descriptors, codecs, and provider contracts shared by Host and Client | — |
registry/ | Stores generated package reflection and live Zod schemas at runtime, plus lookup and Context provider registries | ctx.typert |
Related documentation
- Typert subsystem reference — the literal public contracts recorded from protocol and registry types.
- API Gateway reference — how the generated Remote descriptors become running Host-to-Client calls.
- Remote-call Agent Note — the architecture and transport decisions behind Remote calls.
- Package workspace map — every group in the workspace and what each owns.
Dev Note
Working context for maintainers — click to expand
None.