Update dependency web-vitals to v4 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
web-vitals	^2.1.4 -> ^4.0.0

---

Release Notes

GoogleChrome/web-vitals (web-vitals)

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)

v3.5.2

Compare Source

• Pick the first non-null target for INP attribution (#​421)

v3.5.1

Compare Source

• Add extra guard for PerformanceEventTiming not existing (#​403)

v3.5.0

Compare Source

• Run onLCP callback in separate task (#​386)
• Fix INP durationThreshold bug when set to 0 (#​372)
• Prevent FID entries being emitted as INP for non-supporting browsers (#​368)

v3.4.0

Compare Source

• Make bindReporter generic over metric type (#​359)
• Update INP status in README (#​362)
• Fix Metric types for better TypeScript support (#​356)
• Fix selector for SVGs for attribution build (#​354)

v3.3.2

Compare Source

• Fix attribution types (#​348)
• Safe access navigation entry type (#​290)

v3.3.1

Compare Source

• Export metric rating thresholds in attribution build as well.

v3.3.0

Compare Source

• Export metric rating thresholds, add explicit MetricRatingThresholds type (#​323)
• Trim classname selector (#​328)
• Add link to CrUX versus RUM blog post (#​327)
• Prevent LCP being reported for hidden prerendered pages (#​326)
• Add Server Timing information to docs (#​324)
• Fix link in onINP() thresholds comment (#​318)
• Update web.dev link for onINP() (#​307)
• Add a note about when to load the library (#​305)

v3.1.1

Compare Source

• Defer CLS logic until after onFCP() callback (#​297)

v3.1.0

Compare Source

• Add support for 'restore' as a navigationType (#​284)
• Report initial CLS value when reportAllChanges is true (#​283)
• Defer all observers until after activation (#​282)
• Ignore TTFB for loads where responseStart is zero (#​281)
• Defer execution of observer callbacks (#​278)

v3.0.4

Compare Source

• Clamp LCP and FCP to 0 for prerendered pages (#​270)

v3.0.3

Compare Source

• Ensure attribution object is always present in attribution build (#​265)

v3.0.2

Compare Source

• Set an explicit unpkg dist file (#​261)

v3.0.1

Compare Source

• Use the cjs extension for all UMD builds (#​257)

v3.0.0

Compare Source

• [BREAKING] Add a config object param to all metric functions (#​225)
• [BREAKING] Report TTFB after a bfcache restore (#​220)
• [BREAKING] Only include last LCP entry in metric entries (#​218)
• Update the metric ID prefix for v3 (#​251)
• Move the Navigation Timing API polyfill to the base+polyfill build (#​248)
• Add a metric rating property (#​246)
• Add deprecation notices for base+polyfill builds (#​242)
• Add a new attribution build for debugging issues in the field (#​237, #​244)
• Add support for prerendered pages (#​233)
• Rename the ReportHandler type to ReportCallback, with alias for back-compat (#​225, #​227)
• Add support for the new INP metric (#​221, #​232)
• Rename getXXX() functions to onXXX() (#​222)
• Add a navigationType property to the Metric object (#​219)

---

Configuration

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

🚦 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.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠️ 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: occlusion-mapper/client/package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/styled-components
npm error   styled-components@"^6.1.8" from the root project
npm error
npm error Could not resolve dependency:
npm error peer styled-components@"^5.3.5" from [email protected]
npm error node_modules/media-stream-player
npm error   media-stream-player@"^13.1.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/styled-components
npm error   peer styled-components@"^5.3.5" from [email protected]
npm error   node_modules/media-stream-player
npm error     media-stream-player@"^13.1.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-05-22T20_46_59_066Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-22T20_46_59_066Z-debug-0.log