✨ Add view_update support to developer extension

[mormubis]

Motivation

With the partial_view_updates experimental feature enabled, the SDK now emits view_update events alongside regular view events. Without this change, those events would silently appear in the extension as unstyled/unlabeled — no color, no description, just a raw JSON blob. Since view_update is the whole point of the feature, engineers debugging it need to see these events clearly.

Changes

Added a ViewUpdateDescription component that shows the document version, view name, and a count of changed fields in the event. The color map now recognizes view_update (same blue as view), and event sorting handles the optional date field that view_update carries per the schema.

Also fixed a pre-existing crash in getViewName — new URL(relativeUrl) throws when the URL is a path like /home, which is common in SPAs. Wrapped it in a try/catch and fall back to the raw string.

Test instructions

1. Enable the feature flag: datadogRum.init({ enableExperimentalFeatures: ['partial_view_updates'] })
2. Open the Browser SDK developer extension
3. Interact with the page to generate view updates
4. Verify view_update events appear in blue with a description like View update v3 · /home · 2 fields changed

Checklist

• Tested locally
• Tested on staging
• Added unit tests for this change.
• Added e2e/integration tests for this change.
• Updated documentation and/or relevant AGENTS.md file

🤖 Generated with Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 41bbd47c2f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep undated events out of epoch-based sort

Coercing missing timestamps to 0 makes any event without date sort as if it happened at Unix epoch, so view_update entries with omitted dates are pushed to the bottom and can be dropped by the slice(0, MAXIMUM_LOGGED_EVENTS) retention logic under normal traffic. This regresses the new view_update workflow because recent updates become hard to see or disappear entirely when date is absent.

Useful? React with 👍 / 👎.

[cit-pr-commenter-54b7da]

Bundles Sizes Evolution

📦 Bundle Name	Base Size	Local Size	𝚫	𝚫%	Status
Rum	169.51 KiB	169.51 KiB	0 B	0.00%	✅
Rum Profiler	5.97 KiB	5.97 KiB	0 B	0.00%	✅
Rum Recorder	21.23 KiB	21.23 KiB	0 B	0.00%	✅
Logs	54.70 KiB	54.70 KiB	0 B	0.00%	✅
Rum Slim	127.85 KiB	127.85 KiB	0 B	0.00%	✅
Worker	22.99 KiB	22.99 KiB	0 B	0.00%	✅

🚀 CPU Performance

Action Name	Base CPU Time (ms)	Local CPU Time (ms)	𝚫%
RUM - add global context	0.0021	0.003	+42.86%
RUM - add action	0.0105	0.017	+61.90%
RUM - add error	0.0097	0.0156	+60.82%
RUM - add timing	0.0004	0.0008	+100.00%
RUM - start view	0.0092	0.0153	+66.30%
RUM - start/stop session replay recording	0.0007	0.0011	+57.14%
Logs - log message	0.0139	0.0221	+58.99%

🧠 Memory Performance

Action Name	Base Memory Consumption	Local Memory Consumption	𝚫
RUM - add global context	38.24 KiB	37.93 KiB	-309 B
RUM - add action	64.64 KiB	68.31 KiB	+3.68 KiB
RUM - add timing	36.73 KiB	38.55 KiB	+1.82 KiB
RUM - add error	70.01 KiB	68.81 KiB	-1.20 KiB
RUM - start/stop session replay recording	45.58 KiB	41.10 KiB	-4.47 KiB
RUM - start view	483.88 KiB	484.40 KiB	+539 B
Logs - log message	55.00 KiB	54.88 KiB	-117 B

🔗 RealWorld

[datadog-prod-us1-3]

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage (details)
• Patch Coverage: 0.00%
• Overall Coverage: 76.96% (+0.00%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 60763a1 | Docs | Datadog PR Page | Give us feedback!}