Skip to content

Pulling feat/lighthouse-ci into develop#1265

Open
github-actions[bot] wants to merge 11 commits into
developfrom
feat/lighthouse-ci
Open

Pulling feat/lighthouse-ci into develop#1265
github-actions[bot] wants to merge 11 commits into
developfrom
feat/lighthouse-ci

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 23, 2026

On running against mobile and desktop

GoogleChrome/lighthouse-ci#138 (comment)

ktun95 added 3 commits May 22, 2026 21:03
This change adds a lighthouserc.json file to configure Lighthouse CI.
The configuration specifies the URL to test, the command to start the server, and the upload target.
…ite configs

The preview configuration is added to ensure consistent port settings during preview mode, mirroring the behavior of the server configuration. This change ensures that the application uses the specified port and enforces strict port usage during preview, preventing potential conflicts.
The vite preview command is now configured to use the default port, which simplifies the configuration and allows vite to handle port allocation automatically.
@ktun95
Copy link
Copy Markdown
Collaborator

ktun95 commented May 23, 2026

https://github.com/treosh/lighthouse-ci-action

Might be simpler to use

ktun95 added 3 commits May 26, 2026 09:34
This commit introduces a Lighthouse configuration file (`.lighthouserc.json`) to enable performance testing in the CI environment. The configuration specifies the URL to test, the command to start the server, a pattern to wait for before starting tests, and assertion rules based on Lighthouse recommendations. It also configures the test results to be saved to the filesystem.
The Lighthouse CI workflow is added to the build process to automatically run performance audits on every pull request. This helps to catch performance regressions early and ensures that the application maintains a high level of performance.
The Lighthouse CI autorun command now includes the working directory and configuration path, ensuring that the Lighthouse CI runs correctly in the dfp directory with the correct configuration file.
@codecov
Copy link
Copy Markdown

codecov Bot commented May 26, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.37%. Comparing base (df8993a) to head (aaf51d6).
⚠️ Report is 189 commits behind head on develop.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #1265      +/-   ##
===========================================
- Coverage    94.54%   86.37%   -8.18%     
===========================================
  Files          417      449      +32     
  Lines        22026     4052   -17974     
  Branches      1502      446    -1056     
===========================================
- Hits         20825     3500   -17325     
+ Misses        1201      503     -698     
- Partials         0       49      +49     

see 441 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

ktun95 added 5 commits May 26, 2026 10:03
The lighthouse autorun command requires a github token to be able to post the results to github. This commit adds the github token to the command.
The Lighthouse configuration is updated to utilize temporary public storage for reports, which simplifies sharing and accessibility of the generated reports.
The lighthouserc.json file is no longer needed, so it has been removed.
The .lighthouseci folder is added to .gitignore to prevent local Lighthouse CI reports from being committed to the repository.
The githubToken was removed from the lhci autorun command and instead passed as an environment variable. This change was made to resolve an error where the token was not being properly passed to the lhci autorun command.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant