Maurice
9790ad28e1
The app's own screen now opens on a welcome: the TREK mark, a line about what TREK is, and two clear paths — connect the TREK you already open in the browser, or get TREK Cloud. Both lead to polished screens: the address field with live validation, a shake and haptic on a bad address and a success tick before the server takes over; and a TREK Cloud intro with what it offers and a way in. Screens slide and stagger in, buttons give a tap, and it all respects the safe areas, light and dark, and reduced motion. Self-hosters are unaffected: cloud is its own path, never in the way. New native strings are added across all locales (English placeholders outside en/de, to translate).
@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.