How samydoesit/vue-turbo-starter works
Project type and purpose
• This is a frontend-focused monorepo (managed with pnpm & Turborepo) that hosts:
• Three “apps” (Nuxt3, Storybook, Histoire) for demos and development
• A set of shared packages (UI component library, CSS preset, Pinia store, tsconfig presets)
• Purpose: Provide a starter scaffold for Vue 3/Nuxt 3 projects with integrated style presets, component library, state management, documentation (Storybook/Histoire), tests, and CI/CD.
File structure
• Top-level:
• Config files (.editorconfig, .gitignore, Dockerfiles, ESLint, Prettier, Turborepo)
• CI workflows under .github/workflows (autofix, CI)
• Scripts for release and commit verification
• apps/:
• histoire/ – Histoire playground using Vite, UnoCSS
• nuxt/ – Nuxt 3 SSR app with E2E (Playwright), Vitest, Netlify config
• storybook/ – Storybook v7 server (Go), MDX stories, Netlify config
• packages/:
• ui/ – Vue component library used by all apps
• css-preset/ – UnoCSS preset module
• pinia-store/ – Pinia stores
• tsconfig/ – Shared TypeScript configuration
• Build & deployment:
• Dockerfiles per app
• Netlify config for storybook & nuxt
• Testing:
• Vitest for unit tests
• Playwright for E2E in nuxt
• Test fixtures under each package/app where relevant
Key insights from README
• Tech stack: pnpm, Turborepo, Vue 3, Nuxt 3, Vite, UnoCSS, Storybook, Histoire, Vitest, Playwright
• Each app and package is TypeScript-ready
• Build & run commands, Docker instructions, CI via GitHub Actions
• Demo URLs showing deployed Nuxt & Storybook via Netlify
Elements
• from monorepo → Turborepo/pnpm → build/test tasks
• from packages → apps
• from CI/CD → Docker/Netlify
• Another for “apps”
• Annotations for key frameworks (Vue, Nuxt, Storybook, Histoire)