How raychang/fuelog works
Project type and purpose
• This is a Turborepo‐based monorepo. It hosts:
• One Next.js application (“web”) under apps/web
• A shared React UI component library (@repo/ui)
• Two shared configuration packages: ESLint configs and TypeScript configs
• Purpose: provide a boilerplate starter with centralized code sharing, linting/formatting, type checking, and high-performance builds via Turborepo.
File structure
• Top-level:
• .github: CI workflows, custom chat modes, instructions
• apps/web: Next.js TypeScript app, with app/ folder, CSS, fonts, public assets, config files (next.config.ts, tsconfig.json, eslint.config.mjs)
• packages/ui: shared React components (button, card, code), its own tsconfig and ESLint config
• packages/eslint-config & packages/typescript-config: sharable ESLint rules and tsconfig presets
• turbo.json & pnpm-workspace.yaml & pnpm-lock.yaml: orchestrate tasks and dependencies
• Patterns:
• Monorepo with “apps” (deployable units) vs. “packages” (libraries/configs)
• Next.js app leverages React UI library
• CI/CD configured via GitHub Actions and optional Vercel remote cache
README for additional insights
• Describes apps/packages, core technologies (Next.js, TypeScript, ESLint, Prettier)
• Highlights Turborepo commands (turbo dev, turbo build) and remote caching support with Vercel
• No runtime backend—Next.js handles server-side rendering and routing