Julien Gautier
003dc35f71
CI / scan (pull_request) Successful in 2m58s
CI / commits (pull_request) Successful in 2m58s
CI / check (pull_request) Successful in 4m56s
CI / a11y (pull_request) Successful in 2m17s
Docs site / build (pull_request) Successful in 2m7s
CI / perf (pull_request) Successful in 5m54s
`pnpm docs:dev` failed with two distinct symptoms after #159 forced vite past its vulnerable 5.x line: 1. VitePress refused to boot with `VitePress v1 is not compatible with rolldown-vite. Use VitePress v2 instead.` The previous override `vite@<6.4.2 → >=6.4.2` had no upper bound; pnpm resolved vitepress's `vite ^5.0.0` constraint up to vite 7.3.2, which uses the new rolldown bundler and is explicitly rejected by VitePress 1.x. 2. Even when the server eventually booted on a different port, the console was flooded with `Failed to resolve dependency: dayjs, debug, @braintree/sanitize-url, cytoscape, cytoscape-cose-bilkent` — the vitepress-plugin-mermaid wrapper injects those into `optimizeDeps.include` but they aren't reachable from the workspace root under pnpm's strict isolation (transitives of mermaid, never hoisted). Three changes: * `pnpm.overrides.vite` is now an **unconditional** `>=6.4.2 <7` range (not the previous `<6.4.2 → >=6.4.2` selector). The selector form was a no-op once vite had already resolved into 7.x; the unconditional form forces a downgrade to 6.4.2 across every consumer (vitepress, @nx/vite, @analogjs, Vitest). All six top-level projects still lint, test, and build. * `optimizeDeps.include` simplified to `['mermaid']`. Vite 6's dep optimizer walks Mermaid's transitives automatically once Mermaid itself is included, so the explicit list of children the previous fix carried (#157) becomes redundant. * `dayjs`, `debug`, `@braintree/sanitize-url`, `cytoscape`, `cytoscape-cose-bilkent` are pinned as **top-level devDeps**. The vitepress-plugin-mermaid wrapper expects them at the workspace root; under pnpm's strict isolation a transitive of mermaid isn't reachable from a `optimizeDeps.include` lookup unless the workspace declares it. Pinning silences the resolution warnings without changing the resolved tree (these packages were already present via mermaid). Verification: `pnpm docs:dev` boots clean on :5173, home + ADR pages return 200, no warnings. `pnpm docs:build` succeeds in ~9 s. `pnpm audit --audit-level=moderate` reports zero vulnerabilities. `pnpm exec nx run-many -t lint test build` for the 6 main projects all pass.
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.