How trycourier/courier-designer works
Main Components and Layers
• Monorepo Orchestrator
• pnpm workspaces (pnpm-workspace.yaml)
• Turbo (turbo.json)
• Workspace scripts (pnpm dev, build, test, lint)
• Core Layer
• packages/react-designer
– React components, hooks, types
– Build scripts (esbuild, build.js), PostCSS, Tailwind
– Unit tests (vitest.config.ts)
– E2E tests (playwright.config.ts)
• Framework Adapter
• packages/vue-designer
– Wraps React core for Vue
– Vue single-file component (Editor.vue)
– Build script (build.js)
• Demo/Development Apps
• apps/editor-dev (Vite + React)
– Local dev harness loading react-designer (and optionally vue-designer)
• apps/nextjs-demo (Next.js + Tailwind)
– Brand-editor & Template-editor pages
– API hooks into react-designer providers
• CI/CD Pipelines
• .github/workflows/check-pull-request.yml
• .github/workflows/publish-canary.yml
• .github/workflows/publish-release.yml
• External Services
• npm registry (package publish)
• GitHub (source repo, PRs)
Relationships & Dependencies
• pnpm/Turbo orchestrates all packages and apps, running builds/tests across the monorepo.
• react-designer is the core library:
→ depended on by vue-designer and both demo apps.
• vue-designer wraps and re-exports react-designer for Vue consumers.
• apps/editor-dev imports react-designer directly (for local iteration).
• apps/nextjs-demo imports react-designer providers and components to showcase usage.
• CI workflows trigger on push/PR, run lint/tests via the orchestrator, then publish packages to npm.
Architectural Patterns & Design Principles
• Layered Architecture: Core → Adapter → Application
• Monorepo Workspace: Single source for tooling, versioning, cross-package linkage.
• Separation of Concerns:
• UI logic in react-designer
• Framework binding in vue-designer
• Demo & experimentation in apps
• CI/CD Automation: Validate and publish across layers from one place.
Essential Elements
• Clear component labels (package names, app names, workflow names)