v1.290.1
Débogage
Réglage du silence du getter uniquement pour le message harvestCount
L'avertissement résultant de la tentative de l'agent d'écraser le runtime harvestCount sera correctement désactivé.
Déclaration de soutien
New Relic vous recommande de mettre à niveau l'agent régulièrement pour vous assurer de bénéficier des dernières fonctionnalités et avantages en termes de performances. Les sorties plus anciennes ne seront plus prises en charge lorsqu'elles atteindront la fin de leur vie. Les dates de sortie reflètent la date de publication originale de la version de l'agent.
Les nouveaux agents de navigation sont déployés auprès des clients par petites étapes sur une période donnée. De ce fait, la date à laquelle la sortie devient accessible sur votre compte peut ne pas correspondre à la date de publication d'origine. Veuillez consulter ce dashboard d'état pour plus d'informations.
Conformément à notre politique de prise en charge des navigateurs, la version 1.290.1 de l'agent Browser a été conçue et testée sur ces navigateurs et plages de versions : Chrome 126-136, Edge 126-136, Safari 17-17 et Firefox 128-138. Pour les appareils mobiles, la version 1.290.1 a été créée et testée pour Android OS 16 et iOS Safari 17-18.1.
v1.290.0
Features
Bundler tools exports
An optional Webpack splitChunks cacheGroup matcher is now available for users who build the agent via NPM. This matcher enables de-duplication and merging of the agent's lazy-loaded JavaScript into a single chunk. This single chunk loads post-page render, consistent with the behavior of our pre-built agent for APM and copy/paste implementations.
Set UserAction currentUrl before aggregation end
Set currentUrl on the first event of a user action instead of at the end of aggregation.
Improve lazy-loading optimization
Optimize our pattern to ensure that code-bundlers such as webpack can more effectively tree-shake the output to only include the relevant files needed to run the agent. This specifically helps reduce the bundle size, reduce the amount of lazy files generated, and streamlines "custom" agent builds used with NPM.
API Code Splitting
Split the API method definitions per feature instead of a single file shared across all loader types. This allows each loader to only instantiate the necessary APIs for the features included, and reduce overall bundle size for the "Lite" build as well as custom-built agents with NPM. A shell will still exist for non-initialized APIs to prevent errors from throwing on APIs used without the needed features.
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.290.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 125-135, Edge 125-135, Safari 17-17, and Firefox 127-137. For mobile devices, v1.290.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.
v1.289.0
Caractéristiques
Supprimer le cache de configuration de l'agent et les getters/setters
Supprime les fonctions utilitaires de configuration interne de l'agent. Aucun impact sur la fonctionnalité de l’agent n’est prévu. La taille de la build a été réduite par ce changement de style de codage.
Déclaration de soutien
New Relic vous recommande de mettre à niveau l'agent régulièrement pour vous assurer de bénéficier des dernières fonctionnalités et avantages en termes de performances. Les sorties plus anciennes ne seront plus prises en charge lorsqu'elles atteindront la fin de leur vie. Les dates de sortie reflètent la date de publication originale de la version de l'agent.
Les nouveaux agents de navigation sont déployés auprès des clients par petites étapes sur une période donnée. De ce fait, la date à laquelle la sortie devient accessible sur votre compte peut ne pas correspondre à la date de publication d'origine. Veuillez consulter ce dashboard d'état pour plus d'informations.
Conformément à notre politique de prise en charge des navigateurs, la version 1.289.0 du Browser de l'agent a été conçue et testée sur ces navigateurs et plages de versions : Chrome 125-135, Edge 125-135, Safari 17-17 et Firefox 127-137. Pour les appareils mobiles, la version 1.289.0 a été créée et testée pour Android OS 16 et iOS Safari 17-18.1.
v1.288.1
Débogage
Assurez-vous que le tampon d'événements existe toujours
Assurez-vous que les tampons d'événements existent toujours pour éviter les conditions de concurrence entre le cycle de vie de l'agent et le stockage des données.
Appelez directement le gestionnaire pour soumettre un SM
Cela corrige une mauvaise référence à une fonction parent qui n'est pas accessible.
Déclaration de soutien
New Relic vous recommande de mettre à niveau l'agent régulièrement pour vous assurer de bénéficier des dernières fonctionnalités et avantages en termes de performances. Les sorties plus anciennes ne seront plus prises en charge lorsqu'elles atteindront la fin de leur vie. Les dates de sortie reflètent la date de publication originale de la version de l'agent.
Les nouveaux agents de navigation sont déployés auprès des clients par petites étapes sur une période donnée. De ce fait, la date à laquelle la sortie devient accessible sur votre compte peut ne pas correspondre à la date de publication d'origine. Veuillez consulter ce dashboard d'état pour plus d'informations.
Conformément à notre politique de prise en charge des navigateurs, la version 1.288.1 du Browser de l'agent a été conçue et testée sur ces navigateurs et plages de versions : Chrome 125-135, Edge 125-135, Safari 17-17 et Firefox 127-137. Pour les appareils mobiles, la version 1.288.1 a été créée et testée pour Android OS 15 et iOS Safari 17-18.1.
v1.288.0
Features
Prevent storing session data past session expiry
There may be edge cases where some Session Replay/Session Trace data could be stored even though the agent session has expired. Add instrumentation to detect such occurrences and skip storing these events for the time being.
Introduce isFirstOfSession attribute on InitialPageLoad events
To help support User Journeys, the isFirstOfSession custom attribute will be added to BrowserInteraction events of initial page load kind if the page is the first of a new session.
Bug fixes
Reset notified when replay stops recording
Resolves an issue where JavaScriptError events would be missing the hasReplay attribute after session recording is resumed (for example, from user clicking on another tab/tab going idle and then coming back to it).
Solve race condition in logging abort
If the logging feature aborted before the agent had set up the event buffer, it could throw errors. This was addressed by checking for the presence of the event buffer before running methods against it.
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.288.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 124-134, Edge 124-134, Safari 17-17, and Firefox 126-136. For mobile devices, v1.288.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.
v1.287.0
Features
Change architecture to help enable future Micro Front End support
Update the browser agent to support the future product decisions necessary to support micro front end architecture patterns from a single agent instance. This includes the addition of experimental APIs, intended to be used internally only to help support product development until future general availability (GA) is reached.
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.287.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 124-134, Edge 124-134, Safari 17-17, and Firefox 126-136. For mobile devices, v1.287.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.
v1.286.0
Features
Erase .api property on agent instance
The .api property of full and micro agents have been removed. The browser API methods are instead moved to the agent instance itself for ease of targeted access. This includes a minor fix of runtime loaderType for agents that are re-configured after load.
Reduce noise from mousemove events
There may be an edge case where a site performance can be impacted if the browser agent picked up mousemove events via addEventListener.
Handle duplicate agent APIs
Top-level interaction api calls are only responded to by the first exposed non-micro agent. This was changed to prevent issues for customers that run multiple agents together. The top-level interaction api should only be used to communicate with the main agent on the webpage. API calls on micro agents must instead be directly called on the respective micro agents.
Bug fixes
Patch newrelic event detail
There is an edge case where if there is a listener on the newrelic event (as described in the install docs) and any API call is invoked inside this listener, it will trigger an infinite loop.
Get string className for SVG elements
Change the nearestClass field for SVG elements to be a meaningful string name. The className of such elements is of type SVGAnimatedString and previously resulted in an empty object string.
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.286.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 124-134, Edge 124-134, Safari 17-17, and Firefox 126-136. For mobile devices, v1.286.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.