Enhance frontend exception reporting #688
Merged
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
KKoukiou
force-pushed
the
js-crashes-in-description
branch
from
cf15c5c to
2ffe381
Compare
KKoukiou
changed the title
KKoukiou
force-pushed
the
js-crashes-in-description
branch
from
2ffe381 to
a300c05
Compare
KKoukiou
force-pushed
the
js-crashes-in-description
branch
2 times, most recently
from
2b916ff to
2b12351
Compare
bruno-fs
approved these changes
Oct 14, 2025
KKoukiou
had a problem deploying
to
npm-update
GitHub Actions
Failure
KKoukiou
had a problem deploying
to
npm-update
GitHub Actions
Failure
KKoukiou
force-pushed
the
js-crashes-in-description
branch
from
2b12351 to
c0902c2
Compare
KKoukiou
force-pushed
the
js-crashes-in-description
branch
from
c0902c2 to
a52d189
Compare
Contributor
Author
|
@bruno-fs Obviously after holiday - I would appreciate a second look. |
Contributor
|
Looks good! My only concern is if the stacktrace is too big and the url size exceeds the size allowed by the browser - or if bugzilla has some size limitation as well. |
Contributor
Author
Good point, I will investigate the current limitations. |
bruno-fs
approved these changes
Jan 7, 2026
Contributor
Author
|
I need to rebase this |
KKoukiou
force-pushed
the
js-crashes-in-description
branch
from
a52d189 to
18412f0
Compare
- Simplify getDerivedStateFromError to only set error flag to avoid overwriting front end exceptions as backend ones - Remove redundant componentDidCatch method - Combine window.onerror and window.onunhandledexception handlers
Frontend tracebacks shown in Bugzilla lacked source maps, as window.onerror does not display errors with applied source maps. To address this, integrate the stacktrace-js library to improve the readability of reported frontend exceptions.
KKoukiou
force-pushed
the
js-crashes-in-description
branch
from
18412f0 to
5e63ffd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Frontend tracebacks shown in Bugzilla lacked source maps, as window.onerror does not display errors with applied source maps. To address this, integrate the stacktrace-js library to improve the readability of reported frontend exceptions.
With this commit we have proper tracebacks: