fix(deps): update dependency lighthouse to v7 #134
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^6.0.0
->^7.0.0
Release Notes
GoogleChrome/lighthouse
v7.2.0
Compare Source
Full Changelog
We expect this release to ship in the DevTools of Chrome 90, and to PageSpeed Insights within 2 weeks.
New contributors
Thanks to our new contributors 👽🐷🐰🐯🐻!
Core
Fraggle Rock
Support for auditing user flows (#11313)
Deps
Clients
Docs
Tests
Misc
v7.1.0
Compare Source
Full Changelog
We expect this release to ship in the DevTools of Chrome 90, and to PageSpeed Insights within 2 weeks.
New contributors
Thanks to our new contributors 👽🐷🐰🐯🐻!
Core
Fraggle Rock
Support for auditing user flows (#11313)
CLI
Deps
Tests
Misc
v7.0.1
Compare Source
Full Changelog
We expect this release to ship in the DevTools of Chrome 90, and to PageSpeed Insights within 2 weeks.
New contributors
Thanks to our new contributors 👽🐷🐰🐯🐻!
Core
Fraggle Rock
Support for auditing user flows (#11313)
Report
Deps
I18n
Docs
Tests
Misc
v7.0.0
Compare Source
Full Changelog
Lighthouse 7.0 includes a number of programmatic breaking changes and new audits in the Accessibility and PWA categories. There were some improvements in the accuracy of metric calculations, but it is not expected that Performance scores will change significantly for almost all sites. There may be larger changes in Accessibility and PWA scores due to the new audits.
This release is expected to ship in the DevTools of Chrome 89, and to PageSpeed Insights within 2 weeks.
Notable changes
start_url
respond with 200 when offline. Separately, the "Page load is fast enough on mobile network" audit was removed—while it's no longer part of the PWA section, we encourage folks building a PWA to consult the Performance category to ensure their web app is speedy and delightful.lighthouse@next
on npm. Note that while automated tests pass before publishing, it's expected that this version will be more unstable than the regular releases (#11792, #11805, #11810)axe-core
has been updated to the latest 4.1.1 release. The accessibility audits are now faster, more robust, and include multiple new checks (#11661)New contributors
Thanks to Kohta Ito (@koh110) and Sam Stoelinga (@samos123) for their first contributions!
🆕 New audits
installable-manifest
PWA audit, mentioned above, uses Chrome's own installability criteria so it will always stay in sync with installability requirements (#11745)third-party-facades
looks for third-party embeds in the test page that can be lazy loaded with a static "facade". If the embed isn't necessary for immediate interaction by a user, consider using one of the facades to speed up page load (#11290)aria-treeitem-name
,aria-command-name
,aria-tooltip-name
,aria-meter-name
, andaria-progressbar-name
(#11661)♻️ Removed audits
axe-core
also removes two audits that weren't checking much:layout-table
andvideo-description
(#11661)works-offline
andoffline-start-url
audits were removed as their checks are now covered by the newinstallable-manifest
implementation (#11806)load-fast-enough-for-pwa
audit has also been removed since Lighthouse's existing performance metrics more than cover the needs there (#11764)without-javascript
has been removed (#11711)💥 Breaking changes
--emulated-form-factor
or other emulation-related configuration, you'll need to make changes. The new settings should be considerably simpler to use with custom Lighthouse runners using real devices, Puppeteer, or system-level throttling. See the emulation docs for migration guidance. (#11779)🤖💥 Breaking changes for programmatic users
These changes are unlikely to affect end users, but may be important if you are writing custom configs, plugins, or processing the Lighthouse JSON output.
ConsoleMessages
is a new artifact that is a combination of the oldConsoleMessages
andRuntimeExceptions
artifacts, with some expanded data on items logged to the console.RuntimeExceptions
has been removed (#11663)NodeDetails
property on each element (#11474, #11695, #11752)ImageElements
artifact has been streamlined to better represent the data collected and how it's used (#11703, #11707, #11733)extends: true
was allowed as an alias forextends: 'lighthouse:default'
to extend a config from the default Lighthouse config file. The boolean option has been removed to prepare the way for extending from any valid config file (#11835)🧱 Core
Improvements, bug fixes, clarifications
service-worker
audit to the pwa-optimized group; its path in the JSON and metadata on scope URLs are unchanged (#11798)Internal refactors and improvements
Runtime.evaluate
from function code (#10816)InstallabilityErrors
(#11782)uses-http2
audit (again) (#11777)script-treemap-data
: fix sourceRoot and missing coverage bugs (#11825)Tests
warn-not-offline-capable
in test (#11799)third-party-facades
test (#11786)Misc
uses-http2
: remove mention of h2 push in docs (#11834)redirectPass
to work around crbug (#11813)*.d.ts
files (#11793)git --deepen
if no token (#11785)npm pack
command (#11783)lighthouse-plugin-publisher-ads
in Lightrider (#11648)print-contributors.js
script (#11736)Deps
Renovate configuration
📅 Schedule: "before 3am on Monday" (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.