⚡️ Use native fetch to avoid Zone.js change detection in Angular apps #4117
+74
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Apply
getZoneJsOriginalValue()tofetch()calls inhttpRequest.ts, consistent with how timers and event listeners already bypass Zone.js intimer.tsandaddEventListener.ts.Motivation
In Angular applications, Zone.js patches
fetch()to trigger change detection. Each Datadog beacon currently triggers a full Angular change detection cycle (~5ms), even though telemetry data never affects the UI.Measured impact:
Changes
getZoneJsOriginalValueandgetGlobalObjectinhttpRequest.tsgetNativeFetch()helper functionfetchStrategy()andfetchKeepAliveStrategy()Testing