flights_web/CLAUDE.md

Aeroflot.Flights.Web

Current State

React 18 SSR application built with Modern.js 2.70.8 (Rspack bundler) and Module Federation 2.3.3. The app is a remote frontend component embeddable in the customer's channel apps (Web, PWA).

Stack: Modern.js 2.70.8, React 18.2, Rspack, Module Federation 2.3.3, i18next (9 languages), PrimeReact, Leaflet, SignalR, OpenTelemetry, Vitest, Playwright.

Source: src/ (file-based routing under src/routes/). Legacy Angular 12 SPA in ClientApp/ (read-only reference, not deployed).

Builds: pnpm build:standalone (SSR server at dist/standalone/), pnpm build:remote (MF remote at dist/remote/ with mf-manifest.json).

Dev: pnpm dev (Modern.js on :8081), pnpm dev:full (proxy on :8080 with API forwarding via curl to bypass WAF).

Known constraint: Modern.js 3.x upgrade is blocked by @module-federation/modern-js ESM incompatibilities (broken __filename/require in ESM bundles, missing api.modifyWebpackConfig in Rsbuild 2.0). React Router v7 future flags are enabled to suppress deprecation warnings.

Contractual Requirements

The following are contractual hard constraints for the remote frontend component.

1. Tech Stack

• ModernJS (SSR) for the frontend framework.
• Module Federation 2.0. Any bundler with MF 2.0 support is acceptable: Webpack 5, Rsbuild, Rspack, or Vite.
• Must emit mf-manifest.json at https://<domain>/mf-manifest.json exposing components and logic. Reference: https://module-federation.io/guide/basic/webpack.html.
• React 18+, Concurrent Mode compatible.
• <Suspense> support required when async loading is used.
• Component bodies must be side-effect free — no fetch outside useEffect.
• Dynamic imports must use React.lazy().

2. Data & Integrations

• Consumes customer REST APIs, JSON payloads only.
• Rendered data must stay consistent with API responses (no stale state leaking into the UI).

3. Performance

• Must sustain 100 RPS.

4. Availability & Fault Tolerance

• VMs hosting the component must be geographically distributed.
• 24/7/365 availability; recovery time ≤ 6 hours after infra is restored.

5. Security

• Component must be isolated — no attack surface exposed to other components of the host site.

6. SEO & Accessibility

• SEO optimization required.
• Render microdata: JSON-LD and OpenGraph.
• Web analytics integrations: Yandex.Metrica, CTM, Variocube, Key-Astrom (Dynatrace).

7. Cross-Platform

• Embeddable in multiple channel apps (Web, PWA).
• Fully responsive ("fluid") layout across all screen sizes.

8. Logging & Monitoring

• Frontend log collection in a customer-specified format, shipped to the customer's log aggregation system.
• System event monitoring with export to a metrics aggregator.

9. Module Structure

• Must conform to the customer's standard remote frontend module structure for uniform deployment.

10. Design

• Implement against customer-provided mockups using the customer's design system.
• Must embed other customer remote components when available.

Commit Rules

• Never add Co-Authored-By lines to commit messages.
• Commit messages in English, concise, focused on "why" not "what".
• Commit autonomously when changes are complete and stable — no need to ask for permission. Group related edits into logical commits. Still ask before pushing, force-pushing, or any destructive git operation.

Test Rules

• Every fix must have an e2e test. Before committing a behaviour change, either create a new Playwright spec under tests/e2e/ that exercises the fix, or extend/update the existing spec that covers the affected page. Tests must run green before commit; never commit a fix without proving it through Playwright.