search

INCF / niQC

NeuroImaging Quality Control (niQC)
https://incf.github.io/niQC/
MIT License
13 stars 14 forks source link

Bump chrome-launcher and lighthouse #58

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps chrome-launcher to 0.15.1 and updates ancestor dependency lighthouse. These dependencies need to be updated together.

Updates chrome-launcher from 0.10.5 to 0.15.1

Release notes

Sourced from chrome-launcher's releases.

v0.15.1 (Tue, May 31 2022)

  • 3724165a make launcher.kill() synchronous, fs.rm now gets force and maxRetries (#268)
  • 3561350a revise taskkill procedure on windows (#267)
  • 690ae983 add lighthouse smoketests (windows) to CI (#265)
  • 279577fd docs(chrome-flags-for-tools): add link to overview of features (#235)
  • ff91c18b fix: use wslpath to resolve Windows paths (#200)
  • 30755cde test: run latest versions of node in CI (#257)

v0.15.0 (Wed, Nov 10 2021)

  • 1af60cb add getChromePath() method for printing found chrome path (#255)

v0.14.2 (Tue, Nov 2 2021)

  • ba8d76bd fix chrome connection in node 17, use 127.0.0.1 explicitly (#253)
  • 56731dd8 fix: forward support for fs.rm in node 14.14+ (#242)

v0.14.1

  • 630bb77f feat: set browser preferences (#247)
  • 12b2c8e3 docs(flags): note that disable-gpu isnt needed

v0.14.0 (Tue, May 18 2021)

  • ac1f4aff move to minimum node 12; remove rimraf (#237)
  • dec646c4 deps: remove mkdirp for fs.mkdirSync (#234)
  • 83ab178a update minimum node version (#222)
  • a5f6eb2f add additional chrome flags (#227)
  • 3a7c9610 reword unset-CHROME_PATH error message
  • b1b8dc74 rename disabled TranslateUI to Translate to match Chrome (#225)
  • beb41360 chore: update dependencies and test targets (#221)
  • df9d564a tests: migrate from travis to github actions (#228)
  • 673da08b tests: add mac/win bots to ci (#232)
  • a700ae0c docs: fix readme's getInstallations() section (#212)
  • chrome-flags-for-tools.md update
    • 4b98587d massive update and refactor (#226)
    • e45b100f minor tweaks to headless and others
    • 3a90c21b fix links
    • 8429ca93 add feature flags description
    • 21db5f9f even more documented flags (#231)

0.13.2 (Thu, May 7 2020)

  • 7c1ea547 deps: bump to is-wsl@2.2.0 (#187)
  • 2ae5591d fix: sanitize environment variables used in RegExp (#197)

0.13.1 (Wed, Apr 1 2020)

  • bf2957ac deps: update various dependencies (#192)
    • fixes the vulnerability warnings

0.13.0 (Thu, Feb 27 2020)

  • 83da1e41 feat: add killAll function (#186)
  • b8c89f84 flags: disable the default browser check (#181) (#182)
  • 6112555c fix: log taskkill error based on logging opts (#178) (#179)
  • 7c935efa docs: add missing quote in README.md example (#180)

... (truncated)

Changelog

Sourced from chrome-launcher's changelog.

v0.15.1 (Tue, May 31 2022)

  • 3724165a make launcher.kill() synchronous (#268)
  • 3561350a revise taskkill procedure on windows (#267)
  • 690ae983 add lighthouse smoketests (windows) to CI (#265)
  • 279577fd docs(chrome-flags-for-tools): add link to overview of features (#235)
  • ff91c18b fix: use wslpath to resolve Windows paths (#200)
  • 30755cde test: run latest versions of node in CI (#257)

v0.15.0 (Wed, Nov 10 2021)

  • 1af60cb add getChromePath() method for printing found chrome path (#255)

v0.14.2 (Tue, Nov 2 2021)

  • ba8d76bd fix chrome connection in node 17, use 127.0.0.1 explicitly (#253)
  • 56731dd8 fix: forward support for fs.rm in node 14.14+ (#242)

v0.14.1 (Wed, Oct 6 2021)

  • 630bb77f feat: set browser preferences (#247)
  • 12b2c8e3 docs(flags): note that disable-gpu isnt needed

v0.14.0 (Tue, May 18 2021)

  • ac1f4aff move to minimum node 12; remove rimraf (#237)
  • dec646c4 deps: remove mkdirp for fs.mkdirSync (#234)
  • 83ab178a update minimum node version (#222)
  • a5f6eb2f add additional chrome flags (#227)
  • 3a7c9610 reword unset-CHROME_PATH error message
  • b1b8dc74 rename disabled TranslateUI to Translate to match Chrome (#225)
  • beb41360 chore: update dependencies and test targets (#221)
  • df9d564a tests: migrate from travis to github actions (#228)
  • 673da08b tests: add mac/win bots to ci (#232)
  • a700ae0c docs: fix readme's getInstallations() section (#212)
  • chrome-flags-for-tools.md update
    • 4b98587d massive update and refactor (#226)
    • e45b100f minor tweaks to headless and others
    • 3a90c21b fix links
    • 8429ca93 add feature flags description
    • 21db5f9f even more documented flags (#231)

v0.13.4 (Tue, Jul 7 2020)

  • 08406b28 fix: preserve existing getInstallations output
  • f3669f45 perf: check default paths first when running on Mac (#209)
  • aef94948 docs: update defaultFlags() example for new API (#205)

v0.13.3 (Thu, Jun 4 2020)

  • 6a5d0c72 flags: disable background tracing (#203)
  • d9154291 chore(deps): update typescript and types (#202)

... (truncated)

Commits


Updates lighthouse from 3.2.1 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 👽🐷🐰🐯🐻!

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 👽🐷🐰🐯🐻!

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

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
Maintainer changes

This version was pushed to npm by hoten, a new releaser for lighthouse since your current version.


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](https://github.com/INCF/niQC/network/alerts).
dependabot[bot] commented 1 year ago

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.