Skip to content

Complete framework starter templates (Vite, Next.js, Expo) #42

@PAMulligan

Description

@PAMulligan

Summary

Several framework starter templates are severely incomplete, which will cause pipeline failures when generating projects for those targets.

Current State

Template Files Present Missing
Vite (templates/vite/) vite.config.ts.tpl (1 file) package.json, tsconfig.json, vitest.config.ts.tpl, .storybook/ config
Next.js (templates/nextjs/) next.config.ts (1 file) package.json, tsconfig.json, vitest.config.ts.tpl
Expo (templates/expo/) app.json, package.json, tsconfig.json jest.config.js or vitest config, babel.config.js, .storybook/ config
SvelteKit (templates/sveltekit/) Core files present .storybook/ config
Vue (templates/vue/) Core files present tailwind.config.ts, .storybook/ config

Why This Matters

  • /build-from-figma, /build-from-canva, and /build-from-screenshot all rely on these templates for project scaffolding
  • Incomplete templates mean the pipeline silently produces broken projects
  • Users hitting this will think the pipeline is broken, not the templates

Acceptance Criteria

  • Each template directory contains all files needed for pnpm install && pnpm dev to work
  • Each template has a vitest (or jest for Expo) config
  • Shared configs (templates/shared/) are properly referenced
  • Storybook config exists for all web targets (not React Native)
  • Templates validated by running setup-project.sh for each target

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestgood first issueGood for newcomerspipelineFigma/Canva-to-React conversion pipeline

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions