Makes Lighthouse performance report-only in CI
Continuous Integration / check (pull_request) Successful in 5m56s
Continuous Integration / lighthouse (pull_request) Successful in 12m13s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / deploy-production (pull_request) Skipped

Lighthouse slows the CPU 4x relative to the measuring machine, so the
Raspberry Pi runner scores performance 30-40 points lower than a PC for
the same build. In CI the performance assertions now only warn;
accessibility, best practices and SEO still block, and performance still
blocks in `pnpm check` on a PC. Mobile and desktop reports go to
separate folders and are attached to every run as an artifact.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-19 01:23:06 +02:00
co-authored by Claude Opus 5.5
parent 295adc2a9c
commit 23f7020ff5
11 changed files with 77 additions and 9 deletions
+8 -1
View File
@@ -17,11 +17,18 @@ module.exports = {
...home,
assertions: {
...home.assertions,
'categories:performance': ['error', { minScore: 0.9 }],
'categories:performance': [
base.performanceLevel,
{ minScore: 0.9 },
],
},
},
...rest,
],
},
upload: {
...base.ci.upload,
outputDir: 'lighthouse-reports/desktop',
},
},
};