Maurice
390135f3bc
The old popup was a narrow white card with its own copy of the texts in eight languages, hex colours and a minute counter on the browser clock. The new DemoWelcome is a wide dialog on DialogShell with theme tokens only: what TREK is in one line, the hourly reset with a live countdown in the server's time zone, the 5.0 highlights to try right away (trip planner with bookings and costs, Tours with 3D terrain, TREK Studio photo books, live collaboration, Journey, Atlas, Vacay, Collections, offline use), what the demo leaves out and what the full version adds, and the link to the source. Its strings are real i18n keys in a new demo domain file, translated into all 27 locales. Both dashboards open it instead of the old DemoBanner, which leaves the theme and format baselines with its file and the test non-null assertions it held.
@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.