Skip to content
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.

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

fix(deps): update dependency web-vitals to v4 #1806

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 14, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
web-vitals 3.5.2 -> 4.2.2 age adoption passing confidence

Release Notes

GoogleChrome/web-vitals (web-vitals)

v4.2.2

Compare Source

  • Fix interaction count after bfcache restore (#​505)

v4.2.1

Compare Source

  • Fix compatibility issues with TypeScript v5.5 (#​497)

v4.2.0

Compare Source

  • Refactor INP attribution code to fix errors on Windows 10 (#​495)

v4.1.1

Compare Source

  • Fix pending LoAF cleanup logic (#​493)

v4.1.0

Compare Source

  • Move the support check to the top of the onINP() function (#​490)
  • Fix missing LoAF attribution when entries are dispatched before event entries (#​487)

v4.0.1

Compare Source

  • Add the ReportCallback type back but deprecate it (#​483)

v4.0.0

Compare Source

  • [BREAKING] Update types to support more generic usage (#​471)
  • [BREAKING] Split waitingDuration to make it easier to understand redirect delays (#​458)
  • [BREAKING] Rename TTFBAttribution fields from *Time to *Duration (#​453)
  • [BREAKING] Rename resourceLoadTime to resourceLoadDuration in LCP attribution (#​450)
  • [BREAKING] Add INP breakdown timings and LoAF attribution (#​442)
  • [BREAKING] Deprecate onFID() and remove previously deprecated APIs (#​435)
  • Expose the target element in INP attribution (#​479)
  • Save INP target after interactions to reduce null values when removed from the DOM (#​477)
  • Cap TTFB in attribution (#​440)
  • Fix reportAllChanges behavior for LCP when library is loaded late (#​468)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.


  • 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 enabled auto-merge (squash) May 14, 2024 05:26
Copy link
Contributor Author

renovate bot commented May 14, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: frontend/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: eslint-config-react-app@7.0.1
npm error Found: eslint@9.2.0
npm error node_modules/eslint
npm error   dev eslint@"^9.0.0" from the root project
npm error   peer eslint@"^7.5.0 || ^8.0.0 || ^9.0.0" from @babel/eslint-parser@7.24.5
npm error   node_modules/@babel/eslint-parser
npm error     @babel/eslint-parser@"^7.16.3" from eslint-config-react-app@7.0.1
npm error     node_modules/eslint-config-react-app
npm error       dev eslint-config-react-app@"^7.0.1" from the root project
npm error   3 more (@eslint-community/eslint-utils, ...)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.0.0" from eslint-config-react-app@7.0.1
npm error node_modules/eslint-config-react-app
npm error   dev eslint-config-react-app@"^7.0.1" from the root project
npm error
npm error Conflicting peer dependency: eslint@8.57.0
npm error node_modules/eslint
npm error   peer eslint@"^8.0.0" from eslint-config-react-app@7.0.1
npm error   node_modules/eslint-config-react-app
npm error     dev eslint-config-react-app@"^7.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-07-17T18_32_15_580Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-17T18_32_15_580Z-debug-0.log

@renovate renovate bot force-pushed the renovate/web-vitals-4.x branch from e869df2 to 3601ed0 Compare May 23, 2024 05:39
@renovate renovate bot force-pushed the renovate/web-vitals-4.x branch 2 times, most recently from b613c04 to f951b08 Compare June 11, 2024 04:36
@renovate renovate bot force-pushed the renovate/web-vitals-4.x branch from f951b08 to dedf0fb Compare June 20, 2024 21:55
@renovate renovate bot force-pushed the renovate/web-vitals-4.x branch from dedf0fb to 00339a9 Compare June 30, 2024 21:15
@renovate renovate bot force-pushed the renovate/web-vitals-4.x branch from 00339a9 to 0e34e59 Compare July 17, 2024 18:32
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.

None yet

0 participants