Maurice
6254510e0f
The factories behind the Travel panel's cards (a summary as a poster, a ticket or a sign, a figure on a medal or an odometer, a map of the journey or of one country, a mark as a stamp or a tag, a country as a stamp, a visa or a postcard, each dressed in the book's theme) move to book/travel/book-travel-looks.ts, so the auto layout can build its framing pages from the same looks. Where an element lands stays the caller's: the panel still centres it on the spread on screen, through the same wrapper and the same API, and a designed page names its frame. A mark can now also take an entry's value rather than the journey's.
@trek/shared
Single source of truth for TREK's API contracts, expressed as Zod schemas and consumed by both the server (request validation + inferred DTO types) and the client (typed requests/responses).
This package is part of the incremental NestJS + React 19 migration (see the "Brownfield Rewrite" board). It is intentionally dormant until modules start importing it — adding it changes nothing for users.
Rules
- One folder per domain:
src/<domain>/<domain>.schema.ts(+.spec.ts). - Domain-agnostic building blocks live in
src/common/. - A route is only considered migrated once its contract lives here.
- Schemas are the source of truth; server DTOs and client types are inferred from them
(
z.infer<typeof schema>), never hand-duplicated.
Consumption (dev)
Both apps resolve @trek/shared to this package's TypeScript source:
- Server (
tsx): viapathsinserver/tsconfig.json. - Client (
vite): viaresolve.aliasinclient/vite.config.ts(+pathsfor the type-checker).
Production packaging (Docker / workspace wiring) is introduced in card F2, when the server first depends on this package at runtime. Until then prod builds are untouched.
Not yet here
The canonical error envelope is finalised in card F5 (it must match TREK's current Express error responses byte-for-byte), so it is deliberately not invented in F1.