Skip to content

Commit 7e749c3

Browse files
committed
add migration entry
1 parent da260f2 commit 7e749c3

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

MIGRATION.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -70,3 +70,20 @@ Additionally, we hold ourselves accountable to any security issues, meaning that
7070

7171
Note, that it is decided on a case-per-case basis, what gets backported or not.
7272
If you need a fix or feature in a previous version of the SDK, please reach out via a GitHub Issue.
73+
74+
## 3. Behaviour Changes
75+
76+
### Removal of First Input Delay (FID) Web Vital Reporting
77+
78+
Affected SDKs: All SDKs running in browser applications (`@sentry/browser`, `@sentry/react`, `@sentry/nextjs`, etc.)
79+
80+
In v10, the SDK stopped reporting the First Input Delay (FID) web vital.
81+
This was done because FID has been replaced by Interaction to Next Paint (INP) and is therefore no longer relevant for assessing and tracking a website's performance.
82+
For reference, FID has long been deprecated by Google's official `web-vitals` library and was eventually removed in version `5.0.0`.
83+
Sentry now follows Google's lead by also removing it.
84+
85+
The removal entails **no breaking API changes**. However, in rare cases, you might need to adjust some of your Sentry SDK and product setup:
86+
87+
- Remove any logic in `beforeSend` or other filtering/event processing logic that depends on FID or replace it with INP logic.
88+
- If you set up Sentry Alerts that depend on FID, be aware that these could trigger once you upgrade the SDK, due to a lack of new values.
89+
To replace them, adjust your alerts (or dashbaords) to use INP.

0 commit comments

Comments
 (0)