v1.313.0
Features
Automatically Detect MFE Errors
Add support for automatic Micro Frontend (MFE) attribution of JavaScriptError events. Previously, JavaScriptError events were only ever captured globally by the container browser application. With this change, the agent cross-compares the stack trace of the thrown Error instance 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 stack trace of the thrown Error instance, that event will be attributed to the MFE instead of the container.
remove "withCredentials"
Remove all usage of withCredentials or credentials: 'include' from agent harvests, as cookies have not been used in the agent since before v1220.
Improve MicroFrontEndTiming heuristics
Improve the ability to detect script execution times for MFE, leading to more accurate timeToLoad metrics.
Report CSP violations as new events
Content Security Policy (CSP) violations bubbled up are now captured and reported as a new SecurityPolicyViolation event type to Page Insight consumer. They become query-able through NRQL.
Apply legal and compliance requirements to register API
Ensure the register API complies to company requirements before exposing for limited preview.
Bug fixes
Bad trace.lastTimestamp in Safari + back nav edge case
Fixes a race condition where Safari browser's back navigation (BFCache) could cause absolute timestamps to be recorded at the start of the session trace feature, resulting in an abnormal trace.lastTimestamp value and a mix of relative and absolute timestamps in a single payload.
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.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.313.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.
버전 1.312.1
버그 수정
.at 확장자는 구형 브라우저에서 문제를 일으킵니다.
`.at()` 메서드가 제대로 트랜스파일되지 않아 초기화 문제가 발생하므로 인덱싱으로 변경했습니다.
지지 성명
뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 종료 시점부터 더 이상 지원되지 않습니다. 출시일은 에이전트 버전의 원래 출판일을 반영합니다.
새로운 브라우저 에이전트 릴리스는 일정 기간 동안 작은 단계로 고객에게 출시됩니다. 이로 인해, 귀하의 계정에서 해당 릴리스에 접근할 수 있는 날짜가 원래 게시 날짜와 일치하지 않을 수 있습니다. 자세한 내용은 이 상태 대시보드를 참조하세요.
당사의 브라우저 지원 정책 에 따라, 브라우저 에이전트 v1.312.1은 Chrome 136-146, Edge 136-146, Safari 18-26 및 Firefox 138-148 버전에 맞춰 개발 및 테스트되었습니다. 모바일 장치의 경우 v1.312.1은 Android OS 16 및 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
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.