Julien Gautier
de30299464
CI / commits (pull_request) Successful in 3m8s
CI / scan (pull_request) Successful in 3m22s
CI / check (pull_request) Successful in 5m27s
CI / a11y (pull_request) Successful in 2m4s
Docs site / build (pull_request) Successful in 2m40s
CI / perf (pull_request) Successful in 6m21s
The unconditional `"vite": ">=6.4.2 <7"` override added in #161 to keep VitePress 1.x off rolldown-vite (vite 7+) had the side effect of downgrading **every** vite consumer in the workspace to vite 6.4.2 — including `@angular/build@21.2.11`, whose internal `angular-memory-plugin.js > loadViteClientCode` monkey-patches the Vite client error-overlay code. The patch targets vite 8.x's internal layout; against vite 6 it throws: [vite] Internal server error: Failed to update Vite client error overlay text. at loadViteClientCode (angular-memory-plugin.js:140:31) …on the very first request to `pnpm nx serve portal-shell`. The shell renders a blank screen until the workspace's vite is back to 8.x. Fix: scope the override to vitepress's transitive resolution only, using pnpm's `parent>child` selector syntax. Diff is one line: - "vite": ">=6.4.2 <7", + "vitepress>vite": ">=6.4.2 <7", Post-fix resolutions (verified against pnpm-lock): - VitePress → vite@6.4.2 (Rollup-based, VitePress 1.x compatible) - @angular/build, @nx/vite, Vitest, etc. → vite@8.0.13 (restored) - @vitejs/plugin-basic-ssl (analog dep) → vite@7.3.2 (its own peer range; not the patched-7+ rolldown branch in a way that affects us — it's used for HTTPS-cert generation only, not dev-server hosting). Verification: * `pnpm audit --audit-level=moderate` → no known vulnerabilities. * `pnpm docs:build` → 9.5 s, Mermaid still renders in ADR-0009. * `pnpm nx run-many -t lint test build` on the 6 main projects → all green. * `pnpm nx serve portal-shell` → boots cleanly, HTTP 200 on `/`, no `loadViteClientCode` error in the dev log.
Documentation index
This is the entry point to all project documentation. It is maintained automatically: any addition, rename, or removal of a .md file under docs/ must be reflected here in the same change.
Conventions
- Documentation is written in English.
- One topic per file. Group related files into a folder when there are three or more.
- Cross-reference with relative links so they keep working in GitHub, IDEs, and exported sites.
- For architectural decisions, do not add them here — they belong in decisions/ as MADR 4.0.0 ADRs.
Sections
Daily development
- development.md — repo layout, prerequisites, initial setup, daily commands, observability dev-loop (Jaeger UI, log ↔ trace correlation), dependency updates (Renovate), conventional commit cycle. Day-to-day reference for working on the project.
Architecture
- architecture.md — cross-cutting Mermaid diagrams: C4 system context, C4 containers, Nx module boundaries, CI/CD pipeline. Single-decision diagrams (auth sequence, ERD, etc.) live inline in their ADR.
Onboarding & environment
Setup guides for new contributors:
- setup/01-wsl-terminal-setup.md — modern WSL terminal (Zsh + Powerlevel10k + CLI tools)
- setup/02-dev-web-stack.md — Node via nvm, pnpm via corepack, Docker
- setup/03-angular-nx-monorepo.md — Angular + Nx monorepo bootstrap
Operations & runbooks
Empty — to be populated when we deploy.
Security, performance, accessibility
Empty — placeholders to be filled with rationale docs alongside their corresponding ADRs.