Skip to content

Route-level error reporting in error.tsx#847

Open
deslawson wants to merge 1 commit into
rinafcode:mainfrom
deslawson:Bug]-error.tsx-records-breadcrumb-but-never-calls-reportError()-—-errors-silently-dropped-#712

Hidden character warning

The head ref may contain hidden characters: "Bug]-error.tsx-records-breadcrumb-but-never-calls-reportError()-\u2014-errors-silently-dropped-#712"
Open

Route-level error reporting in error.tsx#847
deslawson wants to merge 1 commit into
rinafcode:mainfrom
deslawson:Bug]-error.tsx-records-breadcrumb-but-never-calls-reportError()-—-errors-silently-dropped-#712

Conversation

@deslawson

Copy link
Copy Markdown

Added errorReportingService.reportError(error, ...) call inside the useEffect of src/app/error.tsx, mirroring the pattern in global-error.tsx. The error report includes the full error object, componentStack, and the digest prop when available. Previously, route-level errors only created a breadcrumb without reaching the monitoring backend, making production error triage impossible for the majority of application errors. A corresponding test file (src/app/tests/error.test.tsx) asserts that reportError and addBreadcrumb are both called when the error boundary catches an error.

Closes #712

Description

Brief description of changes

Related Issue

Closes #

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update

Checklist

  • Code follows project style guidelines
  • Self-review completed
  • No console errors
  • Uses Lucide icons consistently
  • Responsive design implemented
  • Starknet best practices followed

@drips-wave

drips-wave Bot commented Jun 29, 2026

Copy link
Copy Markdown

@deslawson Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@RUKAYAT-CODER

Copy link
Copy Markdown
Contributor

Kindly resolve conflict

1 similar comment
@RUKAYAT-CODER

Copy link
Copy Markdown
Contributor

Kindly resolve conflict

Added errorReportingService.reportError(error, ...) call inside the useEffect of src/app/error.tsx, mirroring the pattern in global-error.tsx. The error report includes the full error object, componentStack, and the digest prop when available. Previously, route-level errors only created a breadcrumb without reaching the monitoring backend, making production error triage impossible for the majority of application errors. A corresponding test file (src/app/__tests__/error.test.tsx) asserts that reportError and addBreadcrumb are both called when the error boundary catches an error.

Closes rinafcode#712
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] error.tsx records breadcrumb but never calls reportError() — errors silently dropped

2 participants