How bangumi/frontend works
File-Structure Analysis & Architectural Patterns
• Top-level configuration:
• pnpm-workspace.yaml, package.json, tsconfig.json – define the monorepo.
• GitHub Actions & Husky hooks – CI/CD pipelines for lint, test, build, release.
• Internal packages under packages/:
• design – UI component library (Storybook, theming).
• client – code-generated SDK from api.yaml.
• utils – shared helper functions (BBCode parser, wiki syntax, pages).
• server – placeholder for standalone server logic or Node modules.
• website – the main React/Vite web app with routes, mocks, E2E tests.
• _functions/p1 – serverless functions (e.g., Vercel/Netlify lambda) for API proxies or backend logic.
• Testing frameworks: Vitest for unit, Playwright for e2e, Storybook for visual testing.
Key Architectural Patterns
• Monorepo with PNPM workspace: enforces strict versioning and local linking between packages.
• Serverless microservices: _functions/p1 acts as backend handlers.
• CI/CD via GitHub Actions: separate workflows for lint, unit, e2e, Storybook build, release.
Components
a. Developer & CI/CD
• Local Developer Workstation (pnpm, VSCode, Git)
• GitHub Actions CI/CD
b. Monorepo Controller
• PNPM Workspace & Shared Config
c. Internal Package Modules
• Design System (packages/design)
• OpenAPI Client SDK (packages/client)
• Utility Library (packages/utils)
• Server-side Package (packages/server)
• Website App (packages/website)
d. Serverless Functions
• _functions/p1 handlers
e. External Dependencies
• Third-party APIs (Bangumi API)
• NPM Registry (for package publishes)
f. Testing & Deployment
• Storybook Service
• Playwright E2E environment
• Vercel/Netlify (or target hosting)
Relationships & Data Flows
• Developer → checks out repo → installs via PNPM → edits any package.
• Client SDK makes HTTP calls to serverless functions or external APIs.
• Serverless functions may use packages/server or packages/utils for shared logic.
• CI/CD pipelines run lint/test on all packages → build storybook → publish updated packages → deploy website & functions.
• Website (browser) ↔ Serverless functions (API) ↔ External Bangumi backend.
Essential Callouts
• Monorepo’s dependency graph at the package level.
• Both local developer workflows and automated CI/CD processes.
• Detail the runtime interactions between browser, serverless endpoints, and external APIs.
• Major technologies: React, Vite, TypeScript, Storybook, PNPM, Vitest, Playwright, GitHub Actions.