How yukionishi1129/dailydevapps works
Project type and high-level purpose
• This is a pnpm-managed monorepo (“apps”) that houses:
• A Next.js web application (“webapp”)
• A browser extension (“extension”)
• A shared React/TS component + hook library (“shared”)
• Supporting config packages (eslint-config, prettier-config) and a Storybook site
• Both the webapp and extension consume shared UI components, custom hooks, and GraphQL queries/mutations defined under packages/shared.
File structure for architectural cues
• Top-level files and folders (Dockerfile, docker-compose.yml, Tiltfile) set up local dev containers and services.
• /packages/webapp is a Next.js SSR/CSR client that builds via Vercel (next.config.js, pages/).
• /packages/extension is a WebExtension project built with webpack and runs in Chrome/Firefox as background + content + popup scripts.
• /packages/shared exports common UI, hooks, GraphQL clients, and styling (Tailwind, CSS).
• /packages/storybook hosts a component playground and mock providers.
README for stack and architecture notes
• Monorepo managed by pnpm workspaces
• Node 20.12.0, React + TypeScript
• Next.js for the webapp, Webpack for the extension
• Shared design system + GraphQL client code reused by both clients
• CI/CD via CircleCI and GitHub Actions, deployments to Vercel (webapp) and browser extension stores
Main components and how they interact
A. Clients
• Webapp (Next.js) – SSR pages, dynamic routing, CSR for interactive feeds
• Extension – background script, content script, popup/newtab UI
B. Shared Library (packages/shared)
• React components, hooks, GraphQL queries, styling, utilities
C. External GraphQL API
• daily.dev’s backend GraphQL endpoint (authentication, feed, posts, user data)
D. Third-party Services
• Identity provider (e.g., Ory Kratos) for sign-in/up
• OneSignal (push notifications)
• Analytics/tracking (e.g., gtag.js)
• CDN (serving static assets, SW)
E. Dev & CI/CD Pipeline
• Docker/Docker Compose for local dev (webapp + mock services)
• Tiltfile enables local Kubernetes dev if used
• CircleCI workflows run lint/test/build, deploy preview domains, remove previews on PR close
• Vercel hosts the webapp; extension builds get loaded manually or published to stores
Architectural patterns and design principles
• Monorepo / workspace pattern for cross-project code reuse
• Component library + design system in shared package
• Clear separation of concerns: presentation (React components), data layer (GraphQL hooks), routing (Next.js pages or WebExtension routing)
• SSR + CSR hybrid for the webapp; background + content scripts for the extension
• CI/CD as code (circleci/config.yml, GitHub workflows, vercel.json)