Craig
4dd44b08d0
- lib/scanner.js: native BarcodeDetector + lazy zxing-wasm fallback, ~4fps decode loop, camera teardown in stop() (§8.2 rule 6) - BarcodeScanner.svelte: getUserMedia camera, permission-denied → message + manual barcode text input fallback, stop on first detect + on destroy - App.svelte: §4.1 scan-flow state machine (localFound/offFound/notFound/ error) — local-by-barcode first, OFF lookup → pre-fill FoodEditor → save → log, Refresh-from-OFF button, not-found → manual/search options - FoodEditor.svelte: optional food prop pre-fills from OFF (read-only barcode, source badge), post-save log flow - FoodSearch.svelte: OFF fallback (§4.2) when local results empty - Dashboard.svelte: recent foods quick-log chips - api.js: searchFoodsByBarcode, offRefresh, updateFood, recentFoods - scanner.test.js: 2 unit tests for pure helpers - §8.4 phone checklist deferred to user testing over Caddy HTTPS; manual-barcode + OFF search flows playwright-verified - HANDOFF.md updated: M1+M2 complete, 007 next
CalCount
A personal, self-hosted calorie counter web app with barcode scanning via phone camera and OpenFoodFacts lookup. See SPEC.md for the full spec, data model, API design, and development rules (§8 — read it before writing code).
Stack
- Backend: Python ≥3.12, FastAPI, SQLAlchemy 2, Pydantic 2, SQLite, httpx — managed with uv
- Frontend: Svelte 5 (runes) + Vite 7, zxing-wasm barcode fallback — managed with npm (Node ≥22.12)
Project layout
backend/ FastAPI app (main.py), SQLAlchemy models, Pydantic schemas,
routers/, services/, migrations/, tests/
frontend/ Vite + Svelte SPA (src/), lib/ (api, stores, scanner, format),
components/
Setup
# Backend (uv creates .venv and installs from uv.lock)
cd backend
uv sync
# Frontend
cd frontend
npm install
Run
Two terminals:
# Terminal 1 — backend on http://localhost:8000
cd backend
uv run uvicorn main:app --reload
# Terminal 2 — frontend on http://localhost:5173 (proxies /api → :8000)
cd frontend
npm run dev
The SQLite database (backend/calcount.db) is created and migrated
automatically on backend startup (backend/migrations/).
Test
cd backend && uv run pytest # backend suite
cd frontend && npm test # frontend suite (vitest)
Build
cd frontend && npm run build # production build to frontend/dist/