✨ feat: enable INP subparts collection by default#4371
Conversation
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage (details) 🔗 Commit SHA: 137f8cb | Docs | Datadog PR Page | Was this helpful? React with 👍/👎 or give us feedback! |
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Bundles Sizes Evolution
🚀 CPU Performance
🧠 Memory Performance
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 137f8cb01d
ℹ️ 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".
| START_STOP_RESOURCE = 'start_stop_resource', | ||
| USE_CHANGE_RECORDS = 'use_change_records', | ||
| USE_INCREMENTAL_CHANGE_RECORDS = 'use_incremental_change_records', |
There was a problem hiding this comment.
Restore deprecated INP_SUBPARTS enum member
Removing ExperimentalFeature.INP_SUBPARTS is a source-compatible break for TypeScript consumers that already reference this exported enum value in app code (for example in addExperimentalFeatures([ExperimentalFeature.INP_SUBPARTS])), and those projects will fail to compile immediately after upgrading even though runtime behavior is now default-on. Keeping the enum member as a deprecated no-op alias avoids this avoidable upgrade break while still enabling subparts by default.
Useful? React with 👍 / 👎.
Motivation
This PR enables by default INP subparts collection without the need for any feature flag
The code has been introduced #4158
And the change is available behind a flag since v6.27.0 (release notes)
How to query in RUM
Changes
Test instructions
Checklist