Julien Gautier e9b58a62c0
CI / commits (pull_request) Successful in 2m42s
CI / check (pull_request) Successful in 3m4s
CI / scan (pull_request) Successful in 3m2s
CI / a11y (pull_request) Successful in 2m7s
CI / perf (pull_request) Successful in 5m37s
fix(ci): perf job — point Lighthouse at /fr/ and /en/, drop spa fallback
The previous PR enabled `--localize` on the production build, so the
output structure became `dist/apps/portal-shell/browser/{en,fr}/`
with no top-level `index.html`. Two CI breakages followed:

- `nx run portal-shell:serve-static` (lhci's `startServerCommand`)
  was configured with `spa: true`. The `@nx/web:file-server` executor
  reads that as "copy `<staticFilePath>/index.html` to `404.html` for
  SPA fallback". The source file no longer exists, so the executor
  crashes with `ENOENT … copyfile … index.html` and never opens the
  port.
- Even if the server had started, `lighthouserc.js` was targeting
  `http://localhost:4200/` which produces an `http-server` directory
  listing under the new layout. Lighthouse would have run against
  that, not the SPA.

Fixes:

- Drop `spa: true` from the `serve-static` target. The executor no
  longer attempts the missing copy. Deep-link fallback in production
  is the reverse proxy's job (it routes `/{en,fr}/anything` to the
  matching `index.html`); `nx serve-static` is only used for the
  perf gate and for local prod-build inspection of the entry points.
  For deep-link testing in dev, `nx serve` is the right tool.
- Update `lighthouserc.js` `url` list to `['http://localhost:4200/fr/',
  'http://localhost:4200/en/']`, matching the directive in ADR-0019
  that both locales clear the same performance bar.
2026-05-11 17:16:47 +02:00

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:

Operations & runbooks

Empty — to be populated when we deploy.

Security, performance, accessibility

Empty — placeholders to be filled with rationale docs alongside their corresponding ADRs.

S
Description
No description provided
Readme 42 MiB
Languages
TypeScript 85.3%
JavaScript 5.4%
SCSS 4.3%
HTML 3.9%
Shell 0.8%
Other 0.3%