jsdom 31 failed 56 client test files: it simplifies calc() and reads an unset border as none in computed styles, and its File no longer carries what the upload tests hand it. It moves back to 29 with isomorphic-dompurify 3, which needs it; the lockfile is resolved from the one before the bump, so both sit at the root as they did. jsdom stays a root devDependency, so npm keeps the copy vitest resolves at the root. knip 6.45 reports tsconfig-paths, which test.yml loads from the server, as unlisted rather than unresolved; it is the server's dependency. The removed RTL text plugin took one swallowed catch with it, so that ESLint count is lowered to what the tree 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.