feat: diagnostics uncaught sdk errors installed by script #1419
Conversation
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
Contributor
Author
|
bugbot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
Author
|
bugbot run |
1 task
daniel-graham-amplitude
approved these changes
Dec 9, 2025
Mercy811
deleted the
AMP-143673-diagnostics-uncaught-error-script-auto
branch
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.
Summary
https://amplitude.atlassian.net/wiki/spaces/GOV/pages/3501359165/Diagnostics+track+uncaught+SDK+errors#3.-Runtime-stack-trace-filtering-%E2%AD%90%EF%B8%8F
Auto capture uncaught errors originated from Amplitude SDK including Amplitude plugins by comparing the error stack trace. Errors in event callbacks in Amplitude plugins will be captured too. This only works for installing by <script> tag. If any stack frame contains the the script filename, it's considered as a SDK error.
Checklist
Note
Add global listeners to capture uncaught SDK/plugin errors when loaded via <script>, wiring into DiagnosticsClient and snippet to register script URL, plus exports and tests.
diagnostics/uncaught-sdk-errors.tswithregisterSdkLoaderMetadataandenableSdkErrorListenersto recordsdk.error.uncaughtvia globalerror/unhandledrejectionlisteners when errors originate from the SDK script.enableSdkErrorListeners(this)when diagnostics sampling is enabled inDiagnosticsClient.registerSdkLoaderMetadatafromsrc/index.ts.uncaught-sdk-errors.test.ts, and index export test updates.snippet-index.ts, resolve current script URL and callregisterSdkLoaderMetadatato enable origin detection.test-server/diagnostics.htmlto load SDK via script and include buttons/workflows to trigger SDK and non-SDK errors for diagnostics verification.Written by Cursor Bugbot for commit 24d0bde. Configure here.