perfume.js - npm Package Versions

5.0.0-rc.7 (2020-4-24)

• refactor: reduced library kb part II

5.0.0-rc.6 (2020-4-21)

• refactor: reduced library kb part I

5.0.0-rc.5 (2020-4-19)

• feat: added secondary log for LCP/CLS when the page's lifecycle state changes to hidden

5.0.0-rc.4 (2020-4-19)

• fix: solved issue with storageEstimate and created his own event
• fix: removed extra calls for totalBlockingTime

5.0.0-rc.3 (2020-4-18)

• feat: added Total Blocking Time #112

5.0.0-rc.2 (2020-4-16)

• feat: added storageEstimateQuota and storageEstimateUsage to the navigatorInfo results
• fix: added feature detection for clearMarks

5.0.0-rc.1 (2020-4-14)

• feat: enabled PerformanceObserver for all browser
• feat: simplified the analyticsTracker by having all duration value inside the data property

Breaking Changes

Until now, we allowed only Chrome to run the PerformanceObserver interface because of possible cross-browser issues. One in particular related to Firefox 58: https://bugzilla.mozilla.org/show_bug.cgi?id=1403027 Starting from Perfume.js v5.0.0-rc.1, we are going to remove this limitation, and we are going to monitor any new open issues and address them immediately.

Having both duration and data inside the analyticsTracker, it started causing some confusion. Starting from v5, we will keep only data and have any information from duration contained inside data. Please make sure to change the code inside your analyticsTracker.

4.8.1 (2020-2-24)

• feat: added serviceWorkerStatus in navigatorInfo

4.8.0 (2020-2-23)

• feat: added support for Cumulative Layout Shift score #80

4.7.5 (2020-2-22)

• fix: missed new property as reserved words