Create the React application with locked frontend tooling #7

New issue

Open

opened 2026-11-01 20:11:28 +00:00 by viacheslavshuka · 0 comments

viacheslavshuka commented

2026-11-01 20:11:28 +00:00

Owner

The website needs a reproducible browser build before product screens can share components and localization. Establish the frontend toolchain without adding a server-rendered application.

Scope

Use React, strict TypeScript, Vite, Bun installs and scripts, and a committed Bun lockfile. Keep pinned Node available for tools whose supported runtime needs it. Configure shadcn/ui, Base UI, and Tailwind.

Acceptance criteria

A documented locked setup starts the development application and builds static production assets. CI uses frozen installs and rejects a stale dependency lockfile.
Bun manages installs, scripts, and dependency auditing. Vite remains the build tool. Node and Bun are not required as production website servers.
The initial shell supports desktop and mobile browsers, including ordinary browser navigation from bot links. It does not create a separate Telegram Mini App.
Shared components support keyboard interaction and explicit accessible labels. Component-library defaults do not replace workflow accessibility checks.
User-facing text passes through localization support from the start. Russian is the initial interface language. The setup supports Russian plural forms.
Routing, localization packages, and file placement are implementation choices documented with the resulting configuration. They do not add product policies.
Heavy route features can load on demand. The shell does not eagerly import the calendar, all calendar locales, or Premium components.
The developer workflow invokes installed local tools. No script silently downloads a missing executable during an offline hook.

Validation

Build from the committed lockfile in a clean disposable environment. Check a Russian plural example, keyboard navigation, mobile layout, and direct browser navigation. Inspect the production chunks to confirm the calendar is absent from the base shell.

#10: Generate and verify OpenAPI and the TypeScript client

The website needs a reproducible browser build before product screens can share components and localization. Establish the frontend toolchain without adding a server-rendered application. ## Scope Use React, strict TypeScript, Vite, Bun installs and scripts, and a committed Bun lockfile. Keep pinned Node available for tools whose supported runtime needs it. Configure shadcn/ui, Base UI, and Tailwind. ## Acceptance criteria - A documented locked setup starts the development application and builds static production assets. CI uses frozen installs and rejects a stale dependency lockfile. - Bun manages installs, scripts, and dependency auditing. Vite remains the build tool. Node and Bun are not required as production website servers. - The initial shell supports desktop and mobile browsers, including ordinary browser navigation from bot links. It does not create a separate Telegram Mini App. - Shared components support keyboard interaction and explicit accessible labels. Component-library defaults do not replace workflow accessibility checks. - User-facing text passes through localization support from the start. Russian is the initial interface language. The setup supports Russian plural forms. - Routing, localization packages, and file placement are implementation choices documented with the resulting configuration. They do not add product policies. - Heavy route features can load on demand. The shell does not eagerly import the calendar, all calendar locales, or Premium components. - The developer workflow invokes installed local tools. No script silently downloads a missing executable during an offline hook. ## Validation Build from the committed lockfile in a clean disposable environment. Check a Russian plural example, keyboard navigation, mobile layout, and direct browser navigation. Inspect the production chunks to confirm the calendar is absent from the base shell. ## Related work - [#10: Generate and verify OpenAPI and the TypeScript client](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/10)

viacheslavshuka referenced this issue

2026-11-01 20:11:30 +00:00

Enforce frontend correctness and report runtime performance #9

viacheslavshuka referenced this issue

2026-11-01 20:11:30 +00:00

Generate and verify OpenAPI and the TypeScript client #10

viacheslavshuka referenced this issue

2026-11-01 20:11:32 +00:00

Measure browser Web Vitals and sanitized request timing #12

viacheslavshuka referenced this issue

2026-11-01 20:11:33 +00:00

Authenticate Telegram users through protected Quorum sessions #14