-
Notifications
You must be signed in to change notification settings - Fork 509
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(telemetry): add Sentry to client #10005
base: main
Are you sure you want to change the base?
Conversation
6a7d690
to
850d5d7
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This pull request has merge conflicts that must be resolved before it can be merged. |
f13c915
to
54df66c
Compare
This pull request has merge conflicts that must be resolved before it can be merged. |
This pull request has merge conflicts that must be resolved before it can be merged. |
Bundle StatsHey there, this message comes from a github action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
View detailed bundle breakdownAdded
Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
This pull request has merge conflicts that must be resolved before it can be merged. |
Summary
Problem
We don't get notified if users experience JavaScript errors on MDN.
Solution
Add Sentry to the client to capture client-side errors.
How did you test this change?