Skip to content

feat: implement global error boundary and exception handling mechanism#4848

Open
basantnema31 wants to merge 2 commits into
JhaSourav07:mainfrom
basantnema31:fix-global-error-handling
Open

feat: implement global error boundary and exception handling mechanism#4848
basantnema31 wants to merge 2 commits into
JhaSourav07:mainfrom
basantnema31:fix-global-error-handling

Conversation

@basantnema31
Copy link
Copy Markdown

Resolves #4781. This PR implements a global error boundary and exception handling mechanism for the Next.js App Router by introducing \�pp/error.tsx\ and \�pp/global-error.tsx. These boundaries catch rendering and client-side runtime errors, preventing ungraceful crashes and providing a branded terminal-style fallback UI.

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Jun 7, 2026

Someone is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions Bot added the status:blocked This PR is blocked due to a failing CI check. label Jun 7, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 7, 2026

🚨 Hey @basantnema31, the CI Pipeline is failing on this PR and it has been marked as status:blocked.

Please fix the issues before this can be reviewed. Here's how:

1. Run checks locally before pushing:

npm run format:check   # Check Prettier formatting
npm run lint           # Run ESLint
npm run typecheck      # TypeScript type check
npm run test           # Run unit tests (Vitest)
npm run build          # Verify production build passes

2. Auto-fix common issues:

npm run format         # Auto-fix formatting with Prettier
npm run lint -- --fix  # Auto-fix lint errors where possible

3. Check the full failure log here:
👉 View CI Run

Once you push a fix and the CI passes, the status:blocked label will be removed automatically. 💪

@github-actions github-actions Bot removed the status:blocked This PR is blocked due to a failing CI check. label Jun 7, 2026
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.

CRITICAL: Implement Global Error Boundary and Exception Handling Mechanism

1 participant