How epicweb-dev/react-performance works
Project type and purpose
• This is a monorepo hosting a “React Performance” workshop: a main workshop app (epicshop) plus many small React micro-apps (under /examples and /exercises) to teach specific performance topics.
• The README confirms it’s a hands-on learning environment for diagnosing and fixing React performance issues.
File structure
• Top-level:
• package.json, tsconfig.json, eslint.config.js, GitHub workflows (CI/CD)
• public/ (static assets)
• shared/ (reusable utilities and components)
• examples/ (reference implementations)
• exercises/ (interactive labs, each as its own React app)
• epicshop/ (the main workshop UI and orchestration)
• epicshop/ contains Dockerfile, fly.yaml, setup and test scripts, config for Playwright, TypeScript, npm – this is your host application.
• Each sub-folder in examples/ and exercises/ is a standalone Vite- or Webpack-powered React + TypeScript app with its own package.json, tsconfig.json, source, tests.
README for additional insights
• Confirms the need for React DevTools, Node/npm, and describes a “npm run setup” to bootstrap the workspace.
• “npm start” launches the live workshop app which dynamically loads each exercise.
• Monorepo Root (scripts & orchestrator)
• epicshop Workshop UI (dev server & production build)
• Exercise Apps (micro-frontends under /exercises)
• Example Apps (reference under /examples)
• Shared Library (/shared)
• Build & Test Infrastructure (Vite configs, Playwright, Jest)
• CI/CD Pipeline (GitHub Actions)
• Deployment Targets (Docker container, Fly.io)
• Runtime Environment (Node.js, npm, browser with devtools)
• Root → epicshop & sub-apps: “npm run setup” links and installs
• epicshop ↔ Shared Library: imports utilities/components
• epicshop → Exercise Apps: dynamic import or iframe load on navigation (micro-frontend pattern)
• Build Infrastructure → epicshop & sub-apps: “vite build” / “webpack” → static assets
• Test Infrastructure → epicshop & sub-apps: Playwright (in-browser tests), Jest (unit/spec tests)
• CI/CD → GitHub Actions: runs lint, build, tests on push
• Deployment: Dockerfile builds container → fly.yaml deploys to Fly.io
c. Architectural patterns & design principles:
• Monorepo for unified versioning & dependency management
• Micro-frontends: each exercise is an isolated React app loaded at runtime
• Shared library for DRY utilities
• CI/CD automation for quality gates
• Containerization for consistent runtime
d. Key technologies & frameworks:
• React + TypeScript + Vite (dev & build)
• Playwright & Jest (testing)
• ESLint, GitHub Actions (CI)
• Docker, Fly.io (deployment)