Files
deepseek-harness/packages/typert
imccyu 1e6deb4f16 test(typert): place the worker fixture on a real package leaf
verify-package-paths reads root-relative packages/* strings in tests and
rejected the fixture's packages/generator, which names the real
packages/typert/generator leaf in the wrong group. The fixture now mirrors
that layout.

Refs #5852
2026-10-11 18:50:25 +08:00
..
2026-10-09 15:13:40 +08:00

description, kind
description kind
The Typert group map: the build-time type-graph generator, runtime registry, Loader integration, and shared Remote protocol that enable typed Host-to-Client calls. package-group

packages/typert

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


Dev Note

Working context for maintainers — click to expand

None.