Skip to content

Update all #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update all #42

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 21, 2022 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
@ampproject/worker-dom 0.33.0 -> 0.36.0 age confidence
ansi-colors 4.1.1 -> 4.1.3 age confidence
ava (source) 4.0.1 -> 4.3.3 age confidence
chai (source) 4.3.6 -> 4.5.0 age confidence
chrome-launcher 0.15.0 -> 0.15.2 age confidence
globby 13.1.1 -> 13.2.2 age confidence
lighthouse 9.3.1 -> 9.6.8 age confidence
mocha (source) 9.2.0 -> 9.2.2 age confidence
np 7.6.0 -> 7.7.0 age confidence
prettier (source) 2.5.1 -> 2.8.8 age confidence
typescript (source) 4.5.5 -> 4.9.5 age confidence

Release Notes

ampproject/worker-dom (@​ampproject/worker-dom)

v0.36.0

Compare Source

v0.35.0

Compare Source

v0.34.0

Compare Source

doowb/ansi-colors (ansi-colors)

v4.1.3

Compare Source

v4.1.2

Compare Source

avajs/ava (ava)

v4.3.3

Compare Source

Add compatibility with Node.js 18.8, thanks @​Brooooooklyn #​3091.

Full Changelog: avajs/ava@v4.3.1...v4.3.3

v4.3.2

Compare Source

v4.3.1

Compare Source

What's Changed

New Contributors

Full Changelog: avajs/ava@v4.3.0...v4.3.1

v4.3.0

Compare Source

What's Changed

Full Changelog: avajs/ava@v4.2.0...v4.3.0

v4.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: avajs/ava@v4.1.0...v4.2.0

v4.1.0

Compare Source

New features

Fixes

New Contributors

Full Changelog: avajs/ava@v4.0.1...v4.1.0

chaijs/chai (chai)

v4.5.0

Compare Source

What's Changed

Full Changelog: chaijs/chai@v4.4.1...v4.5.0

v4.4.1

Compare Source

What's Changed

Full Changelog: chaijs/chai@v4.4.0...v4.4.1

v4.4.0

Compare Source

What's Changed

Full Changelog: chaijs/chai@v4.3.10...v4.4.0

v4.3.10

Compare Source

This release simply bumps all dependencies to their latest non-breaking versions.

What's Changed

Full Changelog: chaijs/chai@v4.3.9...v4.3.10

v4.3.9

Compare Source

Upgrade dependencies.

This release upgrades dependencies to address CVE-2023-43646 where a large function name can cause "catastrophic backtracking" (aka ReDOS attack) which can cause the test suite to hang.

Full Changelog: chaijs/chai@v4.3.8...v4.3.9

v4.3.8

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v4.3.7...v4.3.8

v4.3.7

Compare Source

What's Changed

Full Changelog: chaijs/chai@v4.3.6...v4.3.7

GoogleChrome/chrome-launcher (chrome-launcher)

v0.15.2

Compare Source

  • 76b6a13c Update logLevel option typing (#​295)
  • 60044483 Update headless=chrome flag to headless=new (#​290)
  • b041125a log when connection to existing chrome found for requested port (#​291)
  • f64a7d89 docs(flags): fix description of mock-keychain flag
  • c753ba08 use updating node versions in CI (#​286)
  • 8d1d85dc docs(flags): adjust grouping. add in several features (#​283)
  • 471a97c7 flags: disable optimization guide and media router (#​282)
  • 83f08461 docs(flags): add disable-features=MediaRouter which is surprisingly active
  • 346b3c2c rename master branch references to main (#​280)
  • f618e7e5 docs: a few additions to the flags doc
  • c36bd8dc docs: add OptimizationHints to flags
  • 1cbf8b9a Make LaunchedChrome.kill sync (#​269)

v0.15.1

Compare Source

  • 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)
sindresorhus/globby (globby)

v13.2.2

Compare Source

v13.2.1

Compare Source

v13.2.0

Compare Source

  • Pass deep option to ignore filter to avoid unnecessary recursion (#​251) a0e4028

v13.1.4

Compare Source

  • Fix error when reading inaccessible directories with gitignore: true and suppressErrors: true (#​246) e95da57
  • Remove URL TypeScript type workaround (#​230) 55a3c64

v13.1.3

Compare Source

v13.1.2

Compare Source

GoogleChrome/lighthouse (lighthouse)

v9.6.8

Compare Source

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

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

For more on bfcache, see the web.dev article.

Note: This audit initially will not be available for PageSpeed Insights.

Preventing pasting to inputs

The audit password-inputs-can-be-pasted-into is now paste-preventing-inputs. This audit's logic works just as before, but rather than just considering [type=password] inputs, it now fails if any non-readonly input element prevents the user from pasting. #​14313

Lighthouse documentation is now on developer.chrome.com

Our documentation is no longer hosted on web.dev. For the most up to date audit docs, please go to developer.chrome.com/docs/lighthouse/

💥 Breaking changes

Under the hood, Lighthouse now uses the new user-flow supporting infrastructure by default, even for traditional navigation runs. You can opt out of this by: in the CLI, use --legacy-navigation; in DevTools: check “Legacy Navigation” in the settings menu. If you have a use case that necessitates this escape hatch, please file an issue. We plan to remove this legacy path in 11.0.

For Lighthouse result JSON (LHR) users
Page URLs on the Lighthouse Result

Until now, there were two URL fields to describe a Lighthouse run:

  • requestedUrl: the url given by the users, which Lighthouse instructs Chrome to navigate to
  • finalUrl: the url after any server-initiated HTTP and JS-initiated redirects

This taxonomy cannot account for more complex scenarios, such as JS-initiated redirects, usage of the History API or soft-navigations. They were also ill-defined for timespan and snapshot modes. To account for that, Lighthouse 10.0 now has these URL fields:

  • (changed) requestedUrl: The URL that Lighthouse initially navigated to before redirects. This is the same as it was before for navigation mode, but now it will be undefined in timespan/snapshot.
  • (new) mainDocumentUrl: The URL of the last document requested during a navigation. It does not account for soft navigations or history API events made after the page loads. It is only available in navigation mode, and will be undefined in timespan and snapshot modes.
  • (new) finalDisplayedUrl: The URL displayed in the browser combobox at the end of a Lighthouse run. It accounts for soft navigations and history API events. Available in navigation, timespan, and snapshot modes.
  • (deprecated) finalUrl: Same value as mainDocumentUrl.
Audit changes
  • password-inputs-can-be-pasted-into -> paste-preventing-inputs
  • preload-lcp-image -> prioritize-lcp-image
  • third-party-summary no longer uses a link value for item.entity, instead uses a raw text value
  • full-page-screenshot is no longer an audit, instead it is stored at lhr.fullPageScreenshot. To suppress collection of the full-page screenshot in the CLI, you must migrate from --skip-audits full-page-screenshot to --disable-full-page-screenshot.
For Node users
  • Node 14 is no longer supported, the minimum is now Node 16
  • In case you import paths within the lighthouse node package: lighthouse-core/ and lighthouse-cli/ folders are now simply core/ and cli/
  • Converted from CommonJS to ES modules. You can still use lighthouse in CommonJS by using an dynamic import: await import('lighthouse'). For access to just the lighthouse function in CommonJS, you can also use require('lighthouse/core/index.cjs')
  • The CSV output for Lighthouse is much more useful now. Consult the PR for an example of the new format
  • LHError is now LighthouseError. If you are attempting to catch an error thrown by Lighthouse, be sure to account for this!
Node API changes

The lighthouse function now has better integration with Puppeteer. Use lighthouse(url, flags, config, page) to run Lighthouse, passing an existing Puppeteer.Page handle as page.

The user flow api has moved to the top level node entrypoint and can be imported with import {startFlow} from 'lighthouse'.

New flow.startNavigation() and flow.endNavigation() functions let you define a user triggered navigation without any callback function. See the user flow docs for an example.

To change settings for a single user flow step, define the settings overrides on the toplevel flags options flow.snapshot({skipAduits: ['uses-http2']}) instead of on the settingsOverride property.

To give a flow step a custom name, use flow.snapshot({name: 'Custom name'}). Previously this was done via stepName.

For Lighthouse customization (custom config, gatherers, audits)
  • To work in Lighthouse 10.0, custom gatherers will need to implement the new Gatherer interface (an example). Otherwise, they will only work in legacy navigation mode and older versions of Lighthouse
  • Lighthouse cannot use passes to load the page multiple times in navigation mode anymore. If you need to load the page multiple times, we recommend using a user flow. See our config docs for instructions on how to convert to the new config format
  • The ScriptElements artifact is now Scripts, with a slightly different shape
  • Audit.makeOpportunityDetails and Audit.makeTableDetails now accept an options object as the third parameter. This ends up being a breaking change for just Audit.makeOpportunityDetails.

v9.6.7

Compare Source

Full Changelog

This is an npm-only release. We have no plans to release this specific version to DevTools or PSI, but the changes will be rolled up into the next release in those clients.

Core

  • core(trace-elements): include LCP type in artifact (#​14344)
  • core: add priority to network-requests debug audit (#​14340)

v9.6.6

Compare Source

Full Changelog

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

New Contributors

Thanks to our new contributor 👽🐷🐰🐯🐻!

Core

  • unsized-images: ignore non-network SVGs (#​13737)

Deps

v9.6.5

Compare Source

Full Changelog

This is an npm-only release and affects only the raw JSON report. We have no plans to release this specific version to DevTools or PSI, but the changes will be rolled up into the next release in those clients.

Core

  • core(network-requests): include starting timestamp as debug data (#​14253)
  • core: use trace time origin for main-thread-task time origin (#​14252)

v9.6.4

Compare Source

Full Changelog

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

Deps

  • lighthouse-stack-packs: upgrade to 1.8.2 (#​14218)

Clients

Misc

  • misc: keep scripts package.json in npm (#​14239)

v9.6.3

Compare Source

Full Changelog

This is an npm-only release and affects only the raw JSON report. We have no plans to release this specific version to DevTools or PSI, but the changes will be rolled up into the next release in those clients.

Core

  • network-requests: add frame and preload debug data (#​14161)
  • preload-lcp-image: enrich debugData (#​14155)

v9.6.2

Compare Source

Full Changelog

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

Core

  • driver: fix legacy runner hanging oopifs in some cases (#​14074)

Report

  • avoid really slow regexes for data urls (#​13791)

Clients

  • psi: expose the swapLocale types (#​14062)

Tests

Misc

  • build: fix lightrider report generator bundle (#​14031)

v9.6.1

Compare Source

Full Changelog

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

Core

  • fps: run at the end of timespan/snapshot (#​13989)
  • responsiveness: add element screenshot to INP diagnostic (#​13984)
  • responsiveness: add better INP fallback for old Chrome versions (#​13985)

Report

  • devtools: use absolute positioning for overlay (#​13988)

Tests

  • use origin-agent-cluster to actually test oopifs (#​13777)

v9.5.0

Compare Source

Full Changelog

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

New Contributors

Thanks to our new contributor 👽🐷🐰🐯🐻!

Core

  • full-page-screenshot: leave emulated width unchanged (#​13643)
  • inspector-issues: update sameSiteCookie to cookie (#​13708)
  • script-treemap-data: correct value for size (#​13716)
  • lighthouse-logger: convert to ES modules (#​13720)

⛏️👷 Fraggle Rock

Support for auditing user flows (#​11313)

  • separate audit phase for flows (#​13623)
  • use frame url in gather context (#​13699)
  • add logLevel to config context (#​13681)
  • user-flow: audit flow from artifacts json (#​13715)

Report

  • fix timespan/snapshot sticky header (#​13732)

Deps

Clients

  • convert devtools and lightrider entries to ES modules (#​13722)

Tests

  • add more cases for oopif smoke test (#​13705)
  • devtools: add yarn install timeout (#​13717)
  • devtools: update Lighthouse sniffer for smokes (#​13693)
  • devtools: navigation web test (#​13673)
  • smoke: enable more devtools smoke tests (#​13624)
  • smoke: add _excludes and _runner (#​13707)

Misc

  • support --chrome-flags in run devtools script (#​13625)

v9.4.0

Compare Source

Full Changelog

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

Notable Changes

  • Allow auditing of navigations triggered by user interactions in user flows. See our user flow docs for more info. (#​13496)

Core

  • a11y: change link in category description to web.dev (#​13638)
  • full-page-screenshot: wait for doubleraf, network quiet (#​13663)
  • hreflang: remove eval, import axe valid-langs.js directly (#​13385)
  • inputs: refactor form-elements gatherer (#​13662, #​13671)
  • page-functions: set style in getOuterHTMLSnippet without violating CSP (#​13636)
  • runner: independent gather and audit functions (#​13569)
  • uses-long-cache-ttl: ignore stale-while-revalidate (#​13612)

Report

  • add options onPrintOverride and onSaveFileOverride (#​13529)
  • add options disableFireworks and disableDarkMode (#​13649)
  • add onViewTrace

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 2c17322 to d2b4437 Compare March 6, 2022 17:46
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from ba44c99 to dcae38d Compare March 16, 2022 05:20
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from 837370d to 33ebaea Compare March 26, 2022 06:26
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from c5a5e99 to f16b941 Compare April 6, 2022 03:41
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from 57489e8 to dab1635 Compare April 12, 2022 10:41
@renovate renovate bot force-pushed the renovate/all branch from d501832 to 3e93642 Compare May 15, 2022 21:58
@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from c946304 to 3d1daff Compare June 23, 2022 22:05
@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from d4641a3 to c302c9f Compare January 5, 2024 13:48
@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from 986beed to 16140c6 Compare January 27, 2024 17:48
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from a36091d to a3af94f Compare March 21, 2024 00:19
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from e0eefa9 to 48c1565 Compare May 12, 2024 23:19
@renovate renovate bot force-pushed the renovate/all branch from 48c1565 to 3d4357c Compare May 16, 2024 01:04
@renovate renovate bot force-pushed the renovate/all branch from 3d4357c to d259878 Compare May 25, 2024 04:25
@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from 730150d to 1267544 Compare July 2, 2024 04:40
@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from bf5de40 to c2c2fdc Compare December 20, 2024 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants