Maurice
9932288b04
From #3032, adjusted where it broke: - react and react-dom are pinned in the root overrides; the group raised the workspaces to 19.3.1 and left the override at 19.3.0, so two react-dom versions met in every client test. The override moves along. - @mikro-orm/nestjs kept the old @mikro-orm/core at the root while the server got 7.2.8 of its own, two copies whose types do not match; the lockfile now holds one 7.2.8. - mapbox-gl stays at 3.31: 3.34 drops setRTLTextPlugin from its types, which the map engine uses. - the musl pins of rollup stay at 4.62, the rollup version the lockfile holds.
@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.