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.

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

Update dependency web-vitals to v3 - autoclosed #29

Closed
wants to merge 1 commit into from
Closed

Update dependency web-vitals to v3 - autoclosed #29

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 27, 2022 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
web-vitals ^0.2.4 -> ^3.0.0 age adoption passing confidence

Release Notes

GoogleChrome/web-vitals (web-vitals)

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)

v2.1.4

Compare Source

  • Prevent TTFB from reporting after bfcache restore (#​201)

v2.1.3

Compare Source

  • Only call report if LCP occurs before first hidden (#​197)

v2.1.2

Compare Source

  • Ensure reported TTFB values are less than the current page time (#​187)

v2.1.1

Compare Source

  • Add feature detects to support Opera mini in extreme data saver mode (#​186)

v2.1.0

Compare Source

  • Add batch reporting support and guidance (#​166)

v2.0.1

Compare Source

  • Detect getEntriesByName support before calling (#​158)

v2.0.0

Compare Source

  • [BREAKING] Update CLS to max session window 5s cap 1s gap (#​148)
  • Ensure CLS is only reported if page was visible (#​149)
  • Only report CLS when FCP is reported (#​154)
  • Update the unique ID version prefix (#​157)

v1.1.2

Compare Source

  • Ignore negative TTFB values in Firefox (#​147)
  • Add workaround for Safari FCP bug (#​145)
  • Add more extensive FID feature detect (#​143)

v1.1.1

Compare Source

  • Remove use of legacy API to detect Firefox (#​128)

v1.1.0

Compare Source

  • Fix incorrect UMD config for base+polyfill script (#​117)
  • Fix missing getter in polyfill (#​114)
  • Add support for Set in place of WeakSet for IE11 compat (#​110)

v1.0.1

Compare Source

  • Fix missing typings declaration (#​90)

v1.0.0

Compare Source

  • [BREAKING] Add support for reporting metrics on back/forward cache restore (#​87)
  • [BREAKING] Remove the isFinal flag from the Metric interface (#​86)
  • Remove the scroll listener to stop LCP observing (#​85)

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
Copy link
Contributor Author

renovate bot commented Nov 27, 2022 •
edited
Loading

⚠ 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: package-lock.json
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/alert@0.1.5
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"^17.0.1" from the root project
npm WARN   13 more (@testing-library/react, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0" from @reach/alert@0.1.5
npm WARN node_modules/@reach/alert
npm WARN   @reach/alert@"^0.1.2" from toasted-notes@3.2.0
npm WARN   node_modules/toasted-notes
npm WARN 
npm WARN Conflicting peer dependency: react@16.14.0
npm WARN node_modules/react
npm WARN   peer react@"^16.8.0" from @reach/alert@0.1.5
npm WARN   node_modules/@reach/alert
npm WARN     @reach/alert@"^0.1.2" from toasted-notes@3.2.0
npm WARN     node_modules/toasted-notes
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/alert@0.1.5
npm WARN Found: react-dom@17.0.1
npm WARN node_modules/react-dom
npm WARN   react-dom@"^17.0.1" from the root project
npm WARN   5 more (@testing-library/react, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react-dom@"^16.8.0" from @reach/alert@0.1.5
npm WARN node_modules/@reach/alert
npm WARN   @reach/alert@"^0.1.2" from toasted-notes@3.2.0
npm WARN   node_modules/toasted-notes
npm WARN 
npm WARN Conflicting peer dependency: react-dom@16.14.0
npm WARN node_modules/react-dom
npm WARN   peer react-dom@"^16.8.0" from @reach/alert@0.1.5
npm WARN   node_modules/@reach/alert
npm WARN     @reach/alert@"^0.1.2" from toasted-notes@3.2.0
npm WARN     node_modules/toasted-notes
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/component-component@0.1.3
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"^17.0.1" from the root project
npm WARN   13 more (@testing-library/react, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.4.0" from @reach/component-component@0.1.3
npm WARN node_modules/@reach/component-component
npm WARN   @reach/component-component@"^0.1.3" from @reach/alert@0.1.5
npm WARN   node_modules/@reach/alert
npm WARN 
npm WARN Conflicting peer dependency: react@16.14.0
npm WARN node_modules/react
npm WARN   peer react@"^16.4.0" from @reach/component-component@0.1.3
npm WARN   node_modules/@reach/component-component
npm WARN     @reach/component-component@"^0.1.3" from @reach/alert@0.1.5
npm WARN     node_modules/@reach/alert
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/component-component@0.1.3
npm WARN Found: react-dom@17.0.1
npm WARN node_modules/react-dom
npm WARN   react-dom@"^17.0.1" from the root project
npm WARN   5 more (@testing-library/react, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react-dom@"^16.4.0" from @reach/component-component@0.1.3
npm WARN node_modules/@reach/component-component
npm WARN   @reach/component-component@"^0.1.3" from @reach/alert@0.1.5
npm WARN   node_modules/@reach/alert
npm WARN 
npm WARN Conflicting peer dependency: react-dom@16.14.0
npm WARN node_modules/react-dom
npm WARN   peer react-dom@"^16.4.0" from @reach/component-component@0.1.3
npm WARN   node_modules/@reach/component-component
npm WARN     @reach/component-component@"^0.1.3" from @reach/alert@0.1.5
npm WARN     node_modules/@reach/alert
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/visually-hidden@0.1.4
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"^17.0.1" from the root project
npm WARN   13 more (@testing-library/react, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0" from @reach/visually-hidden@0.1.4
npm WARN node_modules/@reach/visually-hidden
npm WARN   @reach/visually-hidden@"^0.1.4" from @reach/alert@0.1.5
npm WARN   node_modules/@reach/alert
npm WARN 
npm WARN Conflicting peer dependency: react@16.14.0
npm WARN node_modules/react
npm WARN   peer react@"^16.8.0" from @reach/visually-hidden@0.1.4
npm WARN   node_modules/@reach/visually-hidden
npm WARN     @reach/visually-hidden@"^0.1.4" from @reach/alert@0.1.5
npm WARN     node_modules/@reach/alert
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/visually-hidden@0.1.4
npm WARN Found: react-dom@17.0.1
npm WARN node_modules/react-dom
npm WARN   react-dom@"^17.0.1" from the root project
npm WARN   5 more (@testing-library/react, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react-dom@"^16.8.0" from @reach/visually-hidden@0.1.4
npm WARN node_modules/@reach/visually-hidden
npm WARN   @reach/visually-hidden@"^0.1.4" from @reach/alert@0.1.5
npm WARN   node_modules/@reach/alert
npm WARN 
npm WARN Conflicting peer dependency: react-dom@16.14.0
npm WARN node_modules/react-dom
npm WARN   peer react-dom@"^16.8.0" from @reach/visually-hidden@0.1.4
npm WARN   node_modules/@reach/visually-hidden
npm WARN     @reach/visually-hidden@"^0.1.4" from @reach/alert@0.1.5
npm WARN     node_modules/@reach/alert
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: airbnb-prop-types@2.16.0
npm WARN Found: react@17.0.1
npm WARN node_modules/react
npm WARN   react@"^17.0.1" from the root project
npm WARN   13 more (@testing-library/react, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^0.14 || ^15.0.0 || ^16.0.0-alpha" from airbnb-prop-types@2.16.0
npm WARN node_modules/airbnb-prop-types
npm WARN   airbnb-prop-types@"^2.16.0" from enzyme-adapter-utils@1.14.0
npm WARN   node_modules/enzyme-adapter-utils
npm WARN 
npm WARN Conflicting peer dependency: react@16.14.0
npm WARN node_modules/react
npm WARN   peer react@"^0.14 || ^15.0.0 || ^16.0.0-alpha" from airbnb-prop-types@2.16.0
npm WARN   node_modules/airbnb-prop-types
npm WARN     airbnb-prop-types@"^2.16.0" from enzyme-adapter-utils@1.14.0
npm WARN     node_modules/enzyme-adapter-utils
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: connected-react-router@6.0.0
npm ERR! Found: react@17.0.1
npm ERR! node_modules/react
npm ERR!   react@"^17.0.1" from the root project
npm ERR!   peer react@"*" from @testing-library/react@11.2.2
npm ERR!   node_modules/@testing-library/react
npm ERR!     @testing-library/react@"^11.1.0" from the root project
npm ERR!   12 more (@wojtekmaj/enzyme-adapter-react-17, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.4.0" from connected-react-router@6.0.0
npm ERR! node_modules/connected-react-router
npm ERR!   connected-react-router@"^6.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@16.14.0
npm ERR! node_modules/react
npm ERR!   peer react@"^16.4.0" from connected-react-router@6.0.0
npm ERR!   node_modules/connected-react-router
npm ERR!     connected-react-router@"^6.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-11-27T12_18_54_712Z-debug-0.log

@renovate renovate bot force-pushed the renovate/web-vitals-3.x branch from 2383d3a to 0d17c03 Compare November 27, 2022 12:19
@renovate renovate bot changed the title Update dependency web-vitals to v3 Update dependency web-vitals to v3 - autoclosed May 22, 2024
@renovate renovate bot closed this May 22, 2024
@renovate renovate bot deleted the renovate/web-vitals-3.x branch May 22, 2024 23:49
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