feat(analytics): add root error boundary with Plausible error tracking#366
Draft
feat(analytics): add root error boundary with Plausible error tracking#366
Conversation
📊 Build Bundle StatsThe latest build generated the following assets: |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
We lacked visibility into frontend crashes. Any unhandled render error would silently disrupt the app without any notification on our end. To address this, we added a root error boundary that captures these errors and sends a privacy-safe event to Plausible.
Changes
RootErrorBoundaryclass component to catch unhandled render errors and display a fallback UI.frontend_errorevent in Plausible witherror_typeandcomponentproperties (no user data is sent).<App />inmain.tsxwithRootErrorBoundary.