feat(browser)!: Send session status unhandled instead of crashed for unhandled errors#22475
Conversation
…for unhandled errors
|
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 6ba3cd5. Configure here.
size-limit report 📦
|
Lms24
left a comment
There was a problem hiding this comment.
LGTM in terms of behaviour!
One suggestion: To save some bytes of bundle size, WDYT about storing the respective status as a property instead of a method?
yup makes sense! updated in d8f97f4 |
| if (shouldUpdateAndSend) { | ||
| updateSession(session, { | ||
| ...(crashed && { status: 'crashed' }), | ||
| ...(crashed && { status: this._unhandledSessionStatus }), |
There was a problem hiding this comment.
last nit (feel free to ignore): Can we name this variable unhandled? Kinda goes nicer with where we take if from (event mechanism.handled) and with the _unhandledSessionStatus property
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 62ba930. Configure here.

continuation of #17849
Unhandled errors don't actually crash the browser, so browser sessions now
report the new
unhandledstatus instead ofcrashed. Node/server sessionsare unchanged and continue to use
crashed.closes #17842