From 77f54dc6f58a6567d48e674b035efabdc9bd96d8 Mon Sep 17 00:00:00 2001 From: Matt Edholm Date: Fri, 8 May 2026 15:50:46 -0400 Subject: [PATCH] chore(ddev): ddev tests now also runs npm run build So the public/build/ bundle that ships in the next deploy always matches the source the tests just verified. Without it, the previous "Remove this frame" feature shipped source-correct but compiled-stale, and the button never appeared on the deployed PWA. Co-Authored-By: Claude Opus 4.7 (1M context) --- .ddev/commands/web/tests | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.ddev/commands/web/tests b/.ddev/commands/web/tests index 2df1617..dcb1984 100755 --- a/.ddev/commands/web/tests +++ b/.ddev/commands/web/tests @@ -16,3 +16,10 @@ echo "── Frontend typecheck + tests ───────────── cd frontend npx vue-tsc --noEmit -p tsconfig.app.json npx vitest run + +echo +echo "── Frontend production build ──────────────────────────" +# Rebuild public/build/ so what gets committed matches what passed tests. +# Without this step, deploys can ship source-correct features whose +# compiled bundle is stale (verified failure mode 2026-05-09). +npm run build