Maurice
de3b2a6ac7
Book a night to check in at ten, pin a stop to three in the afternoon behind it, and the rail said 13:46. True enough as arithmetic — with no hour of its own the chain works the first stop backwards out of the first one that has one, so three minus a fourteen minute drive minus an hour standing there — and nothing anybody asked for. A door that opens at ten, with nothing ahead of it deciding otherwise, IS the hour: the day starts there and runs forwards. Reached later it stays what it was, a floor, and a floor below the arrival changes nothing — which is what keeps a hotel behind an afternoon stop at its real arrival instead of dragging it back to its check-in.
@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.