[fixme] main conflicts with v7#4608
Merged
gh-worker-dd-devflow-36fce6[bot] merged 4 commits intoMay 12, 2026
Merged
Conversation
Introduce the `@datadog/browser-debugger` package, which provides Live Debugger support in browser applications. Frontend developers can attach log probes to running applications, evaluate conditions, and inspect runtime state without redeploying or modifying source code. The package is published privately for now (excluded from generated docs via `typedoc.json`). The probe execution pipeline lives entirely on the client: instrumented code calls into hooks exposed on `globalThis` (`$dd_entry`, `$dd_return`, `$dd_throw`, `$dd_probes`), and the SDK is responsible for evaluating probe conditions, capturing snapshots of arguments, locals, return values, and thrown errors, rendering template messages against runtime context, applying per-probe and global rate limits, and shipping the resulting events to the logs intake. To keep that hot path predictable, expressions, conditions, and message templates are compiled once at probe registration and the capture logic enforces explicit depth, collection-size, and string-length bounds. Probes themselves are pulled from a Delivery API via a cursor-based polling client, so probe lifecycle (add/remove/clear) is driven by the backend rather than the page. Event delivery reuses `@datadog/browser-core`'s batch/flush transport infrastructure, which required a small core change: the transport layer now accepts `'dd_debugger'` as a URL-only source override so events route correctly in the intake without widening the public RUM `source` surface. To validate behavior and guard against regressions, the change also introduces E2E scenarios covering snapshot delivery, value capture, exception handling, template and condition evaluation, and RUM correlation, plus a dedicated instrumentation-overhead benchmark that stress-tests the hooks against the real built bundle (rather than stubs) so the per-call cost we track is the cost customers will actually pay.
🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage (details) 🔗 Commit SHA: a5aca42 | Docs | Datadog PR Page | Give us feedback! |
Bundles Sizes Evolution
🚀 CPU PerformancePending... 🧠 Memory PerformancePending... |
Collaborator
|
/resume |
|
View all feedbacks in Devflow UI.
The v7 branch of browser-sdk has been updated with the latest changes from main |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Note
TL,DR: Fix the conflicts and use
⚠️ Do not mark this pull request as ready for review.
/resumeto merge.We couldn't automatically merge the commit e739e7e329 from main into v7, there is a conflict!
We created this pull request so that you can fix those conflicts by clicking on the
Resolve conflictsbutton at the bottom of this page.If the conflicts are not trivial, you can also resolve them locally by running the following commands in your terminal:
Once you solved the conflicts, you can finish the merge and push your fix by running:
Finally, you can resume the integration of this change by either:
/resumeon this pull request, or clicking on the "Resume" button at the bottom of the page if you have Doggo installed.Alternatively, you can cancel this operation by commenting this pull request with
/resume -c