Skip to content

fix: align performance monitor bundle measurement with CI script (#1050)#1053

Merged
sw-factory-automations merged 1 commit into
mainfrom
feat/1050-align-perf-monitor-bundle-check
May 12, 2026
Merged

fix: align performance monitor bundle measurement with CI script (#1050)#1053
sw-factory-automations merged 1 commit into
mainfrom
feat/1050-align-perf-monitor-bundle-check

Conversation

@sw-factory-automations
Copy link
Copy Markdown
Collaborator

Closes #1050

What

The Performance Monitor automation was measuring bundle sizes by eyeballing pnpm build console output, which uses raw/uncompressed sizes. The CI bundle check (scripts/check-bundle.mjs) reads route-bundle-stats.json and gzips each chunk individually — a different methodology that produces lower, accurate numbers. This caused the weekly report to flag all 12 pages as over-budget while CI passed on the same commit.

How

Updated .ona/automations/performance-monitor.yaml to:

  1. Instruct the agent to run pnpm test:bundle after pnpm build instead of parsing build console output
  2. Parse the structured table from pnpm test:bundle stdout (same script CI uses)
  3. Explicitly warn against estimating sizes from build console output
  4. Updated the report template to match the script's output format (Route, First Load JS (gzip), Budget, Status)

Testing

  • pnpm lint — 0 errors
  • pnpm typecheck — clean
  • pnpm test — 139 files, 1877 tests passed
  • No code changes (YAML-only), so no E2E tests needed
  • W21 report will use the aligned methodology; sizes will match CI output within 1kB tolerance

@vercel
Copy link
Copy Markdown

vercel Bot commented May 12, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
memo Ready Ready Preview, Comment May 12, 2026 0:07am

Request Review

@sw-factory-automations sw-factory-automations merged commit ead4db0 into main May 12, 2026
9 checks passed
@sw-factory-automations sw-factory-automations deleted the feat/1050-align-perf-monitor-bundle-check branch May 12, 2026 12:22
@sw-factory-automations
Copy link
Copy Markdown
Collaborator Author

✅ UI verification skipped — no UI files changed (only .ona/automations/performance-monitor.yaml).

@sw-factory-automations
Copy link
Copy Markdown
Collaborator Author

✅ Post-merge verification passed.

E2E tests (live site):

  • public-routes.spec.ts — 18/18 passed (landing page, sign-in/sign-up validation, auth redirects, SEO routes, health API)
  • auth.spec.ts — 8/8 passed (sign-in, sign-up, sign-out, auth callback, redirects)
  • not-found.spec.ts — 4/4 passed (public and authenticated 404 handling)
  • workspace-home.spec.ts — 6/6 passed (new page, filter, sort, navigation, recently visited)

Ad-hoc smoke tests:

  • ✅ Landing page — loaded, has title, no errors
  • ✅ Sign-in page — email input present
  • ✅ Health endpoint — 200, not reporting down
  • ✅ Authenticated flow — login succeeded, workspace loaded
  • Skipped: /dashboard (not yet built), editor page navigation (no page buttons in test workspace)

No interaction smoke test needed (this is a fix: PR with YAML-only changes).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: performance monitor bundle size measurement diverges from CI bundle check

1 participant