-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Description
First of all: Great Job guys!
I told speckit to do the development in a dev container. It created the following tasks (and implemented them). Looks good, but when trying to evaluate it, I noticed that neither podman-compose up was working nor has it tested it the infrastructure properly.
Phase 1: Setup (Project Initialization)
Purpose: Initialize Vite + React + TypeScript project with Podman development environment
T001 Create Vite + React + TypeScript project at repository root using T001 Create Vite + React + TypeScript project at repository root using npm create vite@latest . -- --template react-ts
T002 [P] Create Podman dev container Containerfile in .devcontainer/Containerfile with Node.js 22 base image
T003 [P] Create podman-compose.yaml in .devcontainer/ with app service and optional n8n-mock service
T004 [P] Configure vite.config.ts with path aliases (@/ for src/), proxy for n8n endpoints, and server host 0.0.0.0
T005 [P] Setup ESLint and Prettier configuration files (.eslintrc.js, .prettierrc)
T006 [P] Create .env.example with VITE_N8N_API_BASE_URL and VITE_N8N_WEBHOOK_URLS placeholders
T007 [P] Install React Flow 11+ dependency: T007 [P] Install React Flow 11+ dependency: npm install @xyflow/react
T008 [P] Install testing dependencies: T008 [P] Install testing dependencies: npm install -D vitest @testing-library/react @testing-library/jest-dom @playwright/test msw
T009 [P] Create basic project structure: src/{components,hooks,services,types,utils}/ and tests/{unit,integration,e2e,mocks}/
T010 [P] Configure Vitest in vitest.config.ts with test environment jsdom
T011 [P] Configure Playwright in playwright.config.ts with sequential execution and fail-fast enabled
T012 [P] Create TypeScript types file in src/types/index.ts for core entities (User, Plant, Flowchart, Asset, Flow, FlowCategory)
T013 Update package.json scripts with dev, build, test, test:e2e, lint, format
Checkpoint: Development environment ready - can start container with podman-compose up
I use github copilot with claude sonnet 4.5
After some conversations it was able to fix it, but the git commits kind of messy:
fix: Correct podman-compose build context for Windows
Changed build context from parent dir (..) to current dir (.)
to fix Containerfile path resolution on Windows Podman.
feat: Add Vite entry point and basic React app
index.html: Vite entry point with root div
src/main.tsx: React root rendering
src/App.tsx: Basic placeholder component
src/index.css: Base styles
Not sure if this is on my side or if some system prompts could be improved to avoid this. A git commit after each implemented task (when testing passed) would be nice.