chore(deps): bump cacheable-request and lighthouse

[dependabot]

Removes cacheable-request. It's no longer used after updating ancestor dependency lighthouse. These dependencies need to be updated together.

Removes cacheable-request

Updates lighthouse from 8.6.0 to 10.0.0

Release notes

Sourced from lighthouse's releases.

v10.0.0

Full Changelog Release article

We expect this release to ship in the DevTools of Chrome 112, and to PageSpeed Insights within 2 weeks.

New Contributors

Thanks to our new contributors 👽🐷🐰🐯🐻!

• Alex N. Jose @​alexnj
• Alexandra White @​heyawhite
• Amanda @​apettenati
• Andrew Gutekanst @​Andoryuuta
• Christopher Holder @​ChristopherPHolder
• Dongkyun Yu (Steve) @​hackurity01
• Floris @​FMJansen
• Gabe @​MrBrain295
• ghost_32 @​k99sharma
• Littleton Riggins @​TripleEquals
• lowkeyAngry @​lowkeyAngry
• Michael McMahon @​TechnologyClassroom
• Shogo Hida @​shogohida
• Stoyan @​stoyan
• Yang Guo @​hashseed

Notable Changes

Performance Score Changes

In the 8.0 release, we described TTI's waning role, and today we have the followup. Time to Interactive (TTI) no longer contributes to the performance score and is not displayed in the report. However, it is still accessible in the Lighthouse result JSON.

Without TTI, the weighting of Cumulative Layout Shift (CLS) has increased from 15% to 25%. See the docs for a complete breakdown of how the Performance score is calculated in 10.0, or play with the scoring calculator.

Types for the Node package

Lighthouse now includes type declarations! Our example TypeScript recipe demonstrates how to achieve proper type safety with Lighthouse.

Third-party Entity classification

Since Lighthouse 5.3, the community-driven third-party-web dataset has been used to summarize how every third-party found on a page contributes to the total JavaScript blocking time, via the third-party-summary audit. With Lighthouse 10.0, we are adding a new property to the JSON result (entities) to make further use of this dataset. Every origin encountered on a page is now classified as first-party or third-party within entities. In 10.0, this classification is used to power the existing third-party filter checkbox.

In a future version of Lighthouse, this will be used to group the table items of every audit based on the entity it originated from, and aggregate the impact of items from that specific entity.

🆕 New Audits

Back/forward cache

The Back/forward cache (bfcache for short) is a browser optimization that serves pages from fully serialized snapshots when navigating back or forwards in session history. There are over 100 different reasons why a page may not be eligible for this optimization, so to assist developers Lighthouse now attempts to trigger a bfcache response and will list anything that prevented the browser from using the bfcache. #14465

... (truncated)

Changelog

Sourced from lighthouse's changelog.

10.0.0 (2023-02-09)

Full Changelog

We expect this release to ship in the DevTools of Chrome 112, and to PageSpeed Insights within 2 weeks.

New Contributors

Thanks to our new contributors 👽🐷🐰🐯🐻!

• Alex N. Jose @​alexnj
• Alexandra White @​heyawhite
• Amanda @​apettenati
• Andrew Gutekanst @​Andoryuuta
• Christopher Holder @​ChristopherPHolder
• Dongkyun Yu (Steve) @​hackurity01
• Floris @​FMJansen
• Gabe @​MrBrain295
• ghost_32 @​k99sharma
• Littleton Riggins @​TripleEquals
• lowkeyAngry @​lowkeyAngry
• Michael McMahon @​TechnologyClassroom
• Shogo Hida @​shogohida
• Stoyan @​stoyan
• Yang Guo @​hashseed

Notable Changes

Performance Score Changes

Time to Interactive (TTI) no longer contributes to the performance score and is not displayed in the report. However, it is still accessible in the Lighthouse result JSON.

Without TTI, the weighting of Cumulative Layout Shift (CLS) has increased from 15% to 25%. See the docs for a complete breakdown of how the Performance score is calculated in 10.0, or play with the scoring calculator.

Types for the Node package

Lighthouse now includes type declarations! Our example TypeScript recipe demonstrates how to achieve proper type safety with Lighthouse.

Entity classification

Since Lighthouse 5.3, the third-party-web dataset has been used to summarize how every third-party found on a page contributes to the total JavaScript blocking time, via the third-party-summary audit. With Lighthouse 10.0, we are adding a new property to the JSON result (entities) to make further use of this dataset. Every origin encountered on a page is now classified as first-party or third-party within entities. In 10.0, this classification is used to power the existing third-party filter checkbox.

In a future version of Lighthouse, this will be used to group the table items of every audit based on the entity it originated from, and aggregate the impact of items from that specific entity.

New Audits

Back/forward cache

• bf-cache (#14465)

The Back/forward cache (bfcache for short) is a browser optimization that serves pages from fully serialized snapshots when navigating back or forwards in session history. There are over 100 different reasons why a page may not be eligible for this optimization, so to assist developers Lighthouse now attempts to trigger a bfcache response and will list anything that prevented the browser from using the bfcache.

... (truncated)

Commits

• 2eb8f34 v10.0.0 (#14594)
• 836271a core(lr): disable bf-cache (#14774)
• 106a963 misc(build): shim unneeded deps in lr report generator (#14773)
• 9107521 tests(e2e): seek translated view trace button (#14772)
• 89d9fb5 core: disconnect Puppeteer when started by Lighthouse (#14770)
• efacda0 i18n: import strings (#14768)
• d890413 misc: allow multiple nightlies to be published in a day (#14767)
• 017ad4e core(config): prevent custom gatherer interference (#14756)
• de6b53a core: rename preload-lcp-image to prioritize-lcp-image (#14761)
• 0b8c63d report: fix sticky table header in DevTools (#14766)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.