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

[renovate]

This PR contains the following updates:

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

---

Release Notes

GoogleChrome/web-vitals (web-vitals)

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
portfolio	❌ Failed (Inspect)			May 13, 2024 11:20pm

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@vercel/[email protected]	None	0	190 kB	vercel-release-bot
npm/[email protected]	None	+3	340 kB	michalsnik
npm/[email protected]	None	+1	11.1 MB	xhmikosr

🚮 Removed packages: npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/[email protected]	Install script: install Source: node-pre-gyp install --fallback-to-build --update-binary	orphan: npm/[email protected]
Install scripts	npm/[email protected]	Install script: postinstall Source: node -e "try{require('./postinstall')}catch(e){}"	orphan: npm/[email protected]
Install scripts	npm/[email protected]	Install script: postinstall Source: node -e "try{require('./postinstall')}catch(e){}"	orphan: npm/[email protected]

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.