Technologies

The concrete stack, the tooling around it, and the conventions that are actually enforced.

Frontend (portal/)

Vue 3.5 + TypeScript, built with Vite 8 (Rolldown bundler). Managed with npm, not pnpm - the one subproject rule people trip on.
State: Pinia for new code; Vuex only as a shrinking legacy layer.
Testing: Vitest 4 + @vue/test-utils + Testing Library, jsdom, co-located .spec.ts, snapshot tests updated via npm run test:snapshot.
Linting: hybrid oxlint first, then ESLint - oxlint owns the eslint-core/typescript-eslint surface, ESLint keeps Vue template rules, Prettier, custom rules. vue-tsc for type-checking. Notable rules: no any, barrel-only imports from @/commonComponents, multi-word component names, max 500 lines per component.
Design system: internal commonComponents library with its own Storybook.
i18n: JSON locale files; permission display names live in en.json under permissionsList.
Path aliases: @ → src, @unified → src/unified, @lotusflare/* → monorepo libs/* packages (auth, billing, catalog, dto, entities...).

Express 4 + TypeScript, HTTPS on port 443 in dev.
Sequelize 6 + MySQL (mysql2); migrations run through scripts/ (npm run db:smart-migrate:enhanced), never raw sequelize-cli.
Auth: Passport (local, passport-azure-ad, passport-okta-oauth); sessions via express-session + connect-session-sequelize.
Redis for caching, Kafka event schemas under eventSchemas/, StatsD metrics.
Testing: Jest with ENV_FILE=./config/.env.test.

The primary runtime config is lf_webapp_config.json, pointed at by APP_CONFIG_PATH. It carries service_hosts_map (URLs of every downstream service), portal_mysql_map (DB endpoints and credentials), Redis, AWS/S3, and StatsD settings.
Feature flags: registry in portalBackend/config/featureFlags.json; enablement per operator in the DB (Tenant Editor), or per user via a cookie endpoint.
Helm-managed env vars are shared by portal and portalBackend; per-DC values live in the env trees.

Run npm run dev in both portal/ and portalBackend/; the SPA dev server is https://portal-dev.lotusflare.com:5173 and needs SSL certs generated by the lf-setup repo.
The recommended path is the Rhino tool, which provisions the full backend environment (MySQL, Redis, Cassandra) locally in one command - connecting a local BFF to remote AWS databases is painfully slow.
routes.json is read once at startup: after editing it, restart portalBackend.

Lint path-scoping: from inside portal/, pass src/... - a repo-root portal/src/... path silently lints zero files.
portalBackend's npm run lint cannot be path-scoped at all - run it unscoped.
New nav pages need the full checklist on both sides: route, router registration, sidebar, locale strings, backend view key, and permission keys - miss one and the page half-exists.