Skip to content

[Snyk] Security upgrade lighthouse from 6.5.0 to 7.4.0 - #29

Open
trabab wants to merge 1 commit into
masterfrom
snyk-fix-d60c1cca163146e63a2ee3b17f72cffc
Open

trabab wants to merge 1 commit into
masterfrom
snyk-fix-d60c1cca163146e63a2ee3b17f72cffc

Conversation

@trabab

@trabab trabab commented Aug 31, 2026

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Uncaught Exception
SNYK-JS-QS-19432019
  738  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Uncaught Exception

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-QS-19432019
@trabab

trabab commented Aug 31, 2026

Copy link
Copy Markdown
Owner Author

Merge Risk: High

This is a major version upgrade from Lighthouse v6 to v7, which introduces significant breaking changes for programmatic users of the Node CLI and module.

Key Breaking Changes:

  • Node API: The function signature for running Lighthouse has changed. The second argument is now an options object, and the config is now a property on that object (options.config). Previously, flags and config were separate arguments. Code using the Node module must be updated to this new structure.
  • LHR (JSON Report) Structure: The structure of the Lighthouse Horizontal Rule (LHR) object has been modified. The audits object is no longer a flat map at the root of the LHR; consumers will need to adjust their parsing logic to account for the new format.
  • Metric Updates: The definition of Cumulative Layout Shift (CLS) has been updated to include shifts from subframes. This may result in different CLS scores and requires re-baselining of performance metrics.
  • Audit Changes: The redirects audit has been removed, and its data is now incorporated into the server-response-time audit.

Recommendation: Developers using the Lighthouse Node module or parsing its JSON output must review the v7.0.0 release notes and update their integrations to support the new API signature and LHR report structure. Thoroughly test and re-baseline performance metrics due to the change in CLS calculation.

Source: Lighthouse v7.0.0 Release Notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

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.

2 participants