Session Handoff: Nuxt Migration — Phase 8 Complete

Date: 2026-03-19 Session Focus: Generate & Deploy pipeline update Context at Handoff: Low — build pipeline updated, ready to push and test CI

What Was Accomplished

Phase 8 — Generate & Deploy

yarn generate verified working — outputs 22 prerendered routes to bab-app-nuxt/.output/public.

Changes Made

generate-version.cjs

Now writes APP_VERSION to BOTH src/version.ts (old Quasar) AND bab-app-nuxt/app/utils/version.ts (Nuxt)

.releaserc.json

prepareCmd: npm run generate-version '${nextRelease.version}' && cd bab-app-nuxt && yarn install --immutable && yarn generate
publishCmd: tar from bab-app-nuxt/.output/public instead of dist/pwa

.gitea/workflows/build.yaml

Removed: yarn dlx @quasar/cli ext invoke @quasar/qcalendar (Quasar CLI step, not needed for Nuxt)
Changed: env file written to bab-app-nuxt/.env instead of .env.local (Nuxt 4 auto-loads .env, not .env.local)

Current State

yarn generate in bab-app-nuxt/ → .output/public/ ✓
CI pipeline updated for Nuxt build
App pages working in dev (Phase 7)

What NEXT Session Should Do

Push to devel or alpha branch and verify CI pipeline succeeds in Gitea
Verify Ansible deploy picks up the new artifact correctly (same tar.gz format, just different content)
Smoke test the deployed app in the target environment

Open Questions

OPEN: Appwrite SDK deprecated API calls — migrate to v14+ signatures? (TS6387 hints in all stores)
OPEN: task/taskTags/skillTags collections — will they ever be created in bab_prod?
OPEN: Should .env.local in bab-app-nuxt/ be removed to avoid confusion with .env?
OPEN: Should nuxt_test branch be merged to main once CI passes, retiring the old Quasar app?

1.9 KiB Raw Blame History