v1.313.1
Bug fixes
Fix method names for MFE methods
Fixes MFE method names which could be minified and unable to be internally tracked for improvements.
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.313.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.313.1 was built and tested for Android OS 16 and iOS Safari 18-26.2.
v1.313.0
Característica
Detectar automáticamente errores de MFE
Agregar soporte para la atribución automática de Micro Frontend (MFE) de eventos JavaScriptError. Anteriormente, los eventos JavaScriptError solo eran capturados globalmente por la aplicación de navegador del contenedor. Con este cambio, el agente compara el rastreo del stack de la instancia de Error lanzada con la firma de la pila de llamadas del módulo MFE que se registró en la API register. Si el archivo responsable de registrarse en el agente del browser se encuentra en el rastreo del stack de la instancia de Error lanzada, ese evento se atribuirá al MFE en lugar de al contenedor.
eliminar "withCredentials"
Elimine todo uso de withCredentials o credentials: 'include' de las cosechas del agente, ya que las cookies no se han utilizado en el agente desde antes de la v1220.
Mejora las heurísticas de MicroFrontEndTiming
Mejorar la capacidad para detectar los tiempos de ejecución de script para MFE, lo que da como resultado métricas de timeToLoad más precisas.
Reportar infracciones de CSP como nuevos eventos
Las infracciones de la Política de seguridad de contenido (CSP) propagadas ahora se capturan y reportan como un nuevo tipo de evento SecurityPolicyViolation al consumidor de información valiosa de la página. Se vuelven consultables a través de NRQL.
Aplicar requisitos legales y de cumplimiento a la API de registro
Asegúrese de que la API de registro cumpla con los requisitos de la empresa antes de exponerla para una vista previa limitada.
Corrección de errores
trace.lastTimestamp incorrecto en Safari + caso extremo de navegación hacia atrás
Corrige una condición de carrera donde la navegación hacia atrás del navegador Safari (BFCache) podía causar que se registraran timestamp absolutos al inicio de la característica de rastreo de sesión, lo que resultaba en un valor trace.lastTimestamp anormal y una mezcla de timestamp relativos y absolutos en una sola carga.
Declaración de apoyo
New Relic recomienda que actualices el agente periódicamente para garantizar que obtengas las últimas características y beneficios de rendimiento. Las versiones anteriores ya no recibirán soporte cuando lleguen al final de su vida útil. Las fechas de lanzamiento reflejan la fecha de publicación original de la versión del agente.
Las nuevas versiones del agente del browser se lanzan a los clientes en pequeñas etapas a lo largo de un periodo de tiempo. Debido a esto, la fecha en que el lanzamiento esté disponible en su cuenta puede no coincidir con la fecha de publicación original. Consulte este dashboard de estado para obtener más información.
De acuerdo con nuestra política de compatibilidad de navegadores, la versión 1.313.0 del agente de Browser se creó y probó para estos navegadores y rangos de versiones: Chrome 136-146, Edge 136-146, Safari 18-26 y Firefox 138-148. Para dispositivos móviles, la v1.313.0 se compiló y probó para Android OS 16 e iOS Safari 18-26.2.
v1.312.1
Bug fixes
.at causes issues in older browsers
.at() is not being properly transpiled and causing initialization issues, switched to indexing.
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.312.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.312.1 was built and tested for Android OS 16 and iOS Safari 18-26.2.
v1.312.0
Features
Automatically Detect MFE Logs
Add support for automatic Micro Frontend (MFE) attribution of Log events. Previously, Log events were only ever automatically captured globally by the container browser application. With this change, the agent cross-compares the call stack signature of the given log method (such as console.log, console.info, etc.) to the call stack signature of the MFE module that registered with the register API. If the file that is responsible for registering with the browser agent is found in the call stack signature of the log method being triggered, that event will be attributed to the MFE instead of the container.
Automatically Detect MFE AJAX
Add support for automatic Micro Frontend (MFE) attribution of AjaxRequest events. Previously, AjaxRequest events were only ever captured globally by the container browser application. With this change, the agent cross-compares the call stack signature of the AJAX call to the call stack signature of the MFE module that registered with the register API. If the file that is responsible for registering with the browser agent is found in the call stack signature of the AJAX request being triggered, that event will be attributed to the MFE instead of the container.
Bug fixes
Session replays not working for Angular app running on Safari
Fixes an issue where session replays would fail to capture any recordings beyond an initial snapshot for Angular apps running on Safari.
Revert circular replacer
The circular replacer method applied to JSON.stringify operations was seen to cause lag in niche cases with deeply complex and nested objects emitted in quick succession such as in scroll event handlers. This method was revert back to a faster simpler operation to decrease performance bottlenecks.
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.312.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.312.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.
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
Corrección de errores
Mejorar la entrada de LCP con valores de atribución de respaldo
En los casos en que se reporta LCP sin una entrada de atribución de web-vitals, el agente ahora transmitirá otros atributos predeterminados proporcionados, como timeToFirstByte, en lugar de ignorarlos.
Declaración de apoyo
New Relic recomienda que actualices el agente periódicamente para garantizar que obtengas las últimas características y beneficios de rendimiento. Las versiones anteriores ya no recibirán soporte cuando lleguen al final de su vida útil. Las fechas de lanzamiento reflejan la fecha de publicación original de la versión del agente.
Las nuevas versiones del agente del browser se lanzan a los clientes en pequeñas etapas a lo largo de un periodo de tiempo. Debido a esto, la fecha en que el lanzamiento esté disponible en su cuenta puede no coincidir con la fecha de publicación original. Consulte este dashboard de estado para obtener más información.
De acuerdo con nuestra política de soporte de navegadores, la v1.310.1 del agente Browser se creó y probó en estos navegadores y rangos de versiones: Chrome 134-144, Edge 134-144, Safari 18-26 y Firefox 137-147. Para dispositivos móviles, la v1.310.1 se compiló y probó para Android OS 16 y 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.