v1.311.0
Features
agentIdentifier removal
Removed scoped references by agent identifier to simplify the agent architecture. All references are now stored directly within the agent reference, eliminating the need to blend agent references with scoped objects via lookup keys.
Attribute original page URL to all PageViewTiming nodes
Expanded pageUrl attribution to all timings, building on previous work for LCP. PageViewTiming events now report the original hard navigation URL for all node types, ensuring data consistency for SPA even if the URL changes before harvest.
improve MFE timing logic
Enhanced the agent's ability to identify the correct MFE script calling the register API. This improvement results in more accurate timing information for MFE environments.
Bug fixes
Enforce string IDs for new MFE registrations
Resolved an issue where non-string IDs caused errors during MFE entity synthesis. The agent now enforces string-based IDs and issues a warning if a different data type is provided.
Circular replacer removed reused objects from harvests
Fixed an issue where the internal stringify method removed shared pointers across harvest payloads, which occasionally caused missing params attributes on error harvests.
Update RegExp to prevent un-minimized webpack build issue
Replaced the $ character with its hexadecimal equivalent in regular expressions. This prevents Webpack from incorrectly replacing the character during the build process, which previously caused agent failures in unminimized builds.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.311.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 134-144, Edge 134-144, Safari 18-26, and Firefox 137-147. For mobile devices, v1.311.0 was built and tested for Android OS 16 and iOS Safari 18-26.
v1.310.1
Bug fixes
Enhance LCP entry with fallback attribution values
In cases wherein LCP is reported with no attribution entry from web-vitals, the agent will now pass on other default provided attributes such as timeToFirstByte instead of ignoring them.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.310.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 134-144, Edge 134-144, Safari 18-26, and Firefox 137-147. For mobile devices, v1.310.1 was built and tested for Android OS 16 and iOS Safari 18-26.
v1.310.0
Features
better MFE timing handling
Improve the detection of script assets reported by the browser which power the MicroFrontEndTiming event's timeToFetch and timeToBeRequested attributes. This change also includes new assetUrl and assetType attributes to better illustrate the assets used to populate the timing data.
Removing old SPA feature & related wrappings entirely
This concludes the complete removal of the old SPA feature that is replaced by Soft Navigations feature. Since agent version 1.307.0, the default "SPA" was already switched over, so no breaking changes from this version are expected.
Capture MFE timings as MicroFrontEndTiming Events
Captures the lifecycle timings of registered entities in preparation for future micro front end product
Bug fixes
Update measure API types
Corrects an issue where the typings associated with the measure API did not accept PerformanceMark as a valid input for start or end values.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.310.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 134-144, Edge 134-144, Safari 17-26, and Firefox 137-147. For mobile devices, v1.310.0 was built and tested for Android OS 16 and iOS Safari 17-26.
v1.309.0
Features
Warn when more than one agent is running
Added a console warning when more than one Browser agent is running on the page.
Improve MFE tag setting
Enforce tags to be set for micro frontends by supplying an object of key-value pairs to the tags argument of the register(...) API. This allows for tags to be specified with an explicit value instead of only supporting boolean tags.
Add WebDriver detection attribute to PageView & PageViewTiming
PageView, PageViewTiming and initialPageLoad-category BrowserInteraction events will now report a webdriverDetected property corresponding to the navigator.webdriver set by the browser.
Bug fixes
Micro agent duplicate handlers
Fixes when micro agents are created in a staggered fashion, handlers for each agent is multiplied by the number of agents that follow. For example if there were two agents, the handlers for the first agent was registered twice. This had the effect of duplicating events + contents of harvest payloads.
allow child registrations from blocked parents
Allow blocked parent entities to still instantiate a child MFE when registering
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.309.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 133-143, Edge 133-143, Safari 17-26, and Firefox 136-146. For mobile devices, v1.309.0 was built and tested for Android OS 16 and iOS Safari 17-26.
v1.308.0
Features
add support for mfe tags with the register API
Adds support for adding entity tags through the usage of the register API
add child.id attribute to facilitate MFE cross-linking
Adds a child.id attribute to duplicated data to facilitate future cross-linking in the UI
Add "deregister" API
Adds support for deregistering a registered entity, for use with the upcoming Micro Front End support initiative.
add parent.type attribute to facilitate relationship synthesis
Adds the required parent.type attribute for future relationship synthesis during MFE ingest.
Add default close reason
Add a default close reason of unknown to WebSocket events whose close reason could not be determined.
Bug fixes
enforce non-null values on the numeric fields
Ensure that numeric fields are always reported on WebSocket events by defaulting to 0 instead of undefined
Clean WebSocket URLs
Remove hash fragments and query params from URLs reported on WebSocket events
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.308.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 133-143, Edge 133-143, Safari 17-26, and Firefox 136-146. For mobile devices, v1.308.0 was built and tested for Android OS 16 and iOS Safari 17-26.
v1.307.0
Features
Make soft navigations feature the default SPA
Soft navigations feature is now the enforced running feature for SPA. The older and deprecated SPA feature cannot be selected or used as of this update.
Add resetSession option to setUserId() API
Introduces option to reset the browser agent session when updating a userid via the setUserId() API.
Ajax deny list wildcard support
Adds wildcard character support, with the * character, to the AJAX deny list feature which allows to substitute one or more characters in your deny list filters.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.307.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 133-143, Edge 133-143, Safari 17-26, and Firefox 136-146. For mobile devices, v1.307.0 was built and tested for Android OS 16 and iOS Safari 17-26.
v1.306.0
Features
Control log API through separate RUM flag
Logs captured by the newrelic.log method will now be configurable through settings and controlled separately from wrapped logs. This allows one to be disabled without affecting the other, as in the case that only newrelic.log is desired and not auto instrumented console.
Ensure responseStart is valid before relying on onTTFB
Adds an extra validation step to ensure that responseStart of the nav timing entry is valid before relying on onTTFB to return valid data. The web-vitals library depends on that value to operate correctly, and without a valid TTFB response, the agent will not send the RUM call. This change ensures that fallback measures are taken when responseStart is invalid, to ensure a RUM call is sent more reliably, which helps compatibility with unsupported frameworks such as ElectronJS.
Bug fixes
Remove linebreak syntax from webpack output
Removes the newline character in webpack output to avoid issues with copy-pasting our script as a string inside code.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.306.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 133-143, Edge 133-143, Safari 17-26, and Firefox 135-145. For mobile devices, v1.306.0 was built and tested for Android OS 16 and iOS Safari 17-26.
v1.305.0
Features
Improve agent compatibility with ChatGPT connector apps
Small tweaks were made to the agent to allow for better compatibility with the unique iframe constraints of ChatGPT connector applications.
Enable user frustrations for Pro/SPA agents
Officially releases dead click and error click detections for interactive elements to Pro and SPA agents.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.305.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 132-142, Edge 132-142, Safari 17-26, and Firefox 135-145. For mobile devices, v1.305.0 was built and tested for Android OS 16 and iOS Safari 17-26.
v1.304.0
Features
Warn message on session reset
Adds a warning code when an agent session reset happens so that we have better debugging on browser transition behavior.
Reduce Session Replay snapshot sizes
Use slimDOMOption = 'all' by default to reduce session replay snapshot payload sizes.
Bug fixes
Observe document.body after document is interactive
Addresses the scenario where MutationObserver.observe() was issued before document.body is available, causing Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'. error.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.304.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 132-142, Edge 132-142, Safari 17-26, and Firefox 134-144. For mobile devices, v1.304.0 was built and tested for Android OS 16 and iOS Safari 17-26.
v1.303.0
Features
Allow consent API to be invoked without localStorage access
Allows the consent API to function without requiring localStorage access, by keeping common state in the agent that controls harvests. Applications must invoke the API on every hard page load when localStorage access is blocked.
Allow nested registrations
To facilitate inherent parent-child relationships with the planned register API, allow registered entities to expose their own .register() API for children of that entity to register with. Entities who register with the container agent will be related to the container. Entities that register under another registered entity will be related to both the container as well as the parent entity.
Additional validation to prepare agent for MFE registrations
Adding validation rules in the agent to prevent bad values for MFE target id and name in support of MFE/v2 registrations.
Add measure support to register API
Adds support for the measure API in the register response object. This is in support of the future micro front end offering planned.
Add useConsentModel functionality
Adds use_consent_mode init property and functionality. Adds the consent() API call. The consent model, if enabled, disallows agent harvesting unless consent is given through the consent() API call.
Retry initial connect call
To help prevent data loss, the agent will now retry the original "RUM" call an extra time for retryable status codes.
Add custom event support to register API
Adds methods for capturing custom events to the register API, to be used later when MFE support is established.
SMs for browser connect response
Adds supportability metrics for failed responses on initializing the page_view_event aggregate.
Bug fixes
Obfuscate custom attributes for logs added after PVE
Extends obfuscation to cover custom attributes on logging events added after the initial RUM/PageViewEvent harvest.
memoize promise context propagation to avoid safari hangs
Memoizes promise context propagation to prevent potential browser hangs in Safari by avoiding repeated context operations.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.303.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 131-141, Edge 131-141, Safari 17-26, and Firefox 134-144. For mobile devices, v1.303.0 was built and tested for Android OS 16 and iOS Safari 17-26.