feat(error): add global-error boundary for root layout crashes - #76
Merged
royalpinto007 merged 1 commit intoAug 8, 2026
Merged
Conversation
|
This is in, @waterlemonnn. Really appreciate it. Contributions like this are what keep agentpostmortem moving. A star on the repo would mean a lot if this project is useful to you. Happy to see more from you whenever you have the time. |
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
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.
Closes #62.
There's no
app/global-error.tsx, so if anything in the root layout itself throws, Next falls back to its built-in error page instead ofapp/error.tsx(which only catches errors below the root layout). In production that's a blank, unbranded page with no way back to the site.This adds
app/global-error.tsxfollowing the acceptance criteria:<html>/<body>since it replaces the root layouthello@agentpostmortem.com)Verified locally by throwing in
app/layout.tsxand runningnpm run dev— the request came back as a 500 that resolved to theapp/global-error.jschunk instead of Next's default error page, then reverted the layout change.