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.
バージョン1.310.1
バグ修正
フォールバック属性値を使用して LCP エントリを強化する
Web-vitals からの属性エントリなしで LCP が報告された場合、エージェントは、 timeToFirstByteなどの他のデフォルトで提供される属性を無視するのではなく、渡すようになりました。
サポートステートメント
New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースはサポート終了になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。
新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、このステータス ダッシュボードをご覧ください。
弊社のブラウザ サポート ポリシーに従い、 Browserの v1.310.1 は、 Chrome 134 ～ 144、Edge 134 ～ 144、Safari 18 ～ 26、Firefox 137 ～ 147 のブラウザとバージョン範囲を対象に構築され、テストされています。 モバイル デバイスの場合、v1.310.1 は Android OS 16 および 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.
バージョン1.308.0
特徴
register APIで mfe タグのサポートを追加
登録APIの使用を通じてエンティティタグを追加するためのサポートを追加します
MFE の相互リンクを容易にするために child.id 属性を追加します
UI での将来の相互リンクを容易にするために、重複したデータに child.id 属性を追加します。
「登録解除」APIを追加
今後の Micro Frontend サポート イニシアチブで使用するために、登録済みエンティティの登録解除のサポートを追加します。
関係の合成を容易にするために parent.type 属性を追加する
MFE 取り込み中の将来の関係合成に必要な parent.type 属性を追加します。
デフォルトのクローズ理由を追加する
終了理由を判別できなかった WebSocket イベントに、デフォルトの終了理由unknownを追加します。
バグ修正
数値フィールドに非NULL値を強制する
WebSocket イベントでは、デフォルトではなく0を設定して、数値フィールドが常にレポートされるようにします。 undefined
クリーンなWebSocket URL
WebSocket イベントで報告された URL からハッシュ フラグメントとクエリ パラメータを削除します。
サポートステートメント
New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースはサポート終了になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。
新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、このステータス ダッシュボードをご覧ください。
弊社のブラウザ サポート ポリシーに従い、 Browserの v1.308.0 は、 Chrome 133 ～ 143、Edge 133 ～ 143、Safari 17 ～ 26、Firefox 136 ～ 146 のブラウザとバージョン範囲を対象に構築され、テストされています。 モバイル デバイスの場合、v1.308.0 は Android OS 16 および 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.