Summary
Several app routes lack an explicit error boundary, leaving failures to surface as the generic app/error.tsx or as an unhandled error.
Affected area
src/app/compare/page.tsx
src/app/governance/page.tsx
src/app/secondary-market/page.tsx
src/app/tax-report/page.tsx
src/app/mobile-properties/page.tsx
src/app/widget/investment-calculator/page.tsx
src/app/developers/tokenize/page.tsx
Steps to reproduce / impact
Trigger a render exception inside one of these pages and you get either a full white page or a generic boundary that doesn't preserve navigation. Users bounce.
Expected behaviour
Wrap each page with withRouteErrorBoundary (already exists in src/components/error/), or migrate to Next.js 14 error boundaries at the route segment level.
Acceptance criteria
Summary
Several app routes lack an explicit error boundary, leaving failures to surface as the generic
app/error.tsxor as an unhandled error.Affected area
src/app/compare/page.tsxsrc/app/governance/page.tsxsrc/app/secondary-market/page.tsxsrc/app/tax-report/page.tsxsrc/app/mobile-properties/page.tsxsrc/app/widget/investment-calculator/page.tsxsrc/app/developers/tokenize/page.tsxSteps to reproduce / impact
Trigger a render exception inside one of these pages and you get either a full white page or a generic boundary that doesn't preserve navigation. Users bounce.
Expected behaviour
Wrap each page with
withRouteErrorBoundary(already exists insrc/components/error/), or migrate to Next.js 14 error boundaries at the route segment level.Acceptance criteria
src/app/**/page.tsxfiles are covered.app/error.tsxwith breadcrumb context.