imccyu
6fbfbb044e
Each of the 61 cases copied the fixture onto disk and ran a full analysis whose four TypeScript programs reloaded the DOM library, @types/node, and zod v4; about 22,000 file-system probes per analysis dominated on a network filesystem. The spec now mocks the node:fs calls the analyzer makes and the ts.sys host for an in-memory workspace, stubs zod and @types/node except in the Emitter case that runs real zod, drops the DOM library from the fixture, and shares the pristine analysis read-only. The file drops from about 316 s to 15 s with the same 61 cases and assertions; the snapshot's external zod path no longer names a pnpm store version. Refs #5852
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 |
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.