Update dependency web-vitals to v3.5.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
web-vitals	3.0.0 -> 3.5.0

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

---

Release Notes

GoogleChrome/web-vitals (web-vitals)

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)

---

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: pnpm-lock.yaml

[06:15:05.111] INFO (9): Installing tool node v18.18.0...
v18.18.0
9.8.1
0.19.0
[06:15:07.553] INFO (9): Installed tool node in 2.4s.
[06:15:08.356] INFO (52): Installing tool pnpm v8.8.0...
8.8.0
[06:15:10.013] INFO (52): Installed tool pnpm in 1.6s.
 ERROR  Unexpected number in JSON at position 7388 while parsing '{  "name": "nextjs-project",  "version' in /tmp/worker/7275b0/6471a9/repos/github/X-oss-byte/Canary-nextjs/package.json 

  183 |     "playwright-chromium": "1.38.1",
  184 |     "plop": "3.0.5",
> 185 |  01-30-Add_test_for_issue_45393
      |  ^
  186 |     "postcss-nested": "4.2.3",
  187 |     "postcss-pseudoelements": "5.0.0",
  188 |     "postcss-short-size": "4.0.0",

For help, run: pnpm help install

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6db569e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR