npm / web-vitals
web-vitals
What changed in web-vitals 5 to 6, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-20.
2 breaking2 new APIs and options3 behavior and defaults1 tooling14 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli initweb-vitals 614 changes
New APIs and options 1
Adds a Resource Timing buffer for LCP attribution, supporting attribution data collection.
Behavior and default changes 3
Small INP interactions are reported with bfcache support.
The default for includeProcessedEventEntries changes to false in v6.
Web Vitals metrics support Soft Navigation when supported by the browser.
Tooling 1
Source maps are added, helping developers trace generated code.
Fixes and other changes 9
Fixes an INP clean-up bug that caused a memory leak.
Fixes negative resourceLoadDuration values in LCP attribution.
Caps pending LoAFs to avoid a memory leak.
Fixes negative inputDelay in INP attribution.
Prevents a spurious CLS report of 0 after bfcache restore.
Guards supportedEntryTypes for older browsers.
Navigation interaction counts are scoped to each InteractionManager.
Prevents a JavaScript error when PerformanceObserver is unavailable.
RequestIdleCallback is capped at 1 second so metrics report even when the browser is busy.
web-vitals 58 changes
Breaking changes 2
Removed getFirstHiddenTimePolyfill.
Removes obsolete FID polyfill types.
New APIs and options 1
Adds the includeProcessedEventEntries option.
Fixes and other changes 5
Fixed errors that could occur when passing the same configuration object to multiple metric functions.
Made the INP interactionTarget setting more robust.
Uses LargestContentfulPaint.id as a fallback when the element is removed from the DOM.
Fixes a bug when onLCP is attached late.
Handles initially hidden pages and onLCP registered on visibility change.