v4.4.2

Bug fixes

• Further mitigations for "performance.getEntriesByName is not a function" errors in some browsers

v4.4.1

Bug fixes

• Add mitigations for "performance.getEntriesByName is not a function" errors in some browsers

v4.4.0

New features

• Rage click detection
• Extra context in the POST beacon allows calculation of user happiness for each beacon

Improvements

• Minification optimisations to reduce bundle size

Bug fixes

• LCP element attribution is stored as the event is received, to prevent missing attribution on discarded elements
• Prevent errors when reading document.documentElement.clientHeight

v4.3.3

Bug fixes

• Fix RUM ID extraction for self-hosted lux.js

v4.3.2

Bug fixes

• Prevent error being thrown when accessing snippetVersion during early unload beacons.
• Prefer to extract the RUM ID from the lux.js script URL i.e. /js/lux.js?id=RUM_ID.

v4.3.0

New features

• Add LUX.on() which can be used to subscribe to internal events. Current events are beacon and new_page_id.
• Add LUX.spaMode which greatly simplifies implementing lux.js in a Single Page Application (SPA). Read the documentation for more information.

Improvements

• Add ES2015 and ES2020 builds which slightly reduce output size. Read the documentation for more information.

v4.2.1

Bug fixes

• Fix case where unload handlers did not send a beacon if they fired after the page visibility had already changed to "hidden".

v4.2.0

Improvements

• Long animation frame entries are sorted by duration, so the slowest entries are prioritised in the payload.

Bug fixes

• Fix metric collectors not being reattached after LUX.init is called.

v4.1.3

Improvements

• Added LUX.maxAttributionEntries to control how many attribution entries are sent in the beacon. The default value has been reduced from 50 to 25 to reduce payload size.
• Long animation frame attribution is sorted by total duration, so the slowest scripts are prioritised in the payload.

v4.1.1

Bug fixes

• Limit the number of LoAF entries and script attribution to prevent large beacon payloads.
• Better handling for legacy browsers that do not support URLSearchParams.