Conversation
nextjs-bot
added
created-by: Next.js team
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
All broken links are now fixed, thank you! |
devjiwonchoi
force-pushed
the
graphite-base/89847
branch
from
486f674 to
e40d1df
Compare
devjiwonchoi
force-pushed
the
jiwon/02-11-docs_catcherror_
branch
from
41c89a9 to
e52b64a
Compare
devjiwonchoi
changed the base branch from
graphite-base/89847
to
jiwon/02-09-docs_error_component_retry_
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
devjiwonchoi
force-pushed
the
jiwon/02-11-docs_catcherror_
branch
from
e52b64a to
780de1b
Compare
This PR adds `unstable_catchError()` API for a granular custom error boundary. The error component generated by this API is not a true component format, as the wrapper provides additional args. Therefore, the API is a function call by design rather than a boundary component to avoid merging the `errorInfo` with the user-provided props from the wrapper. This API works for both the App/Pages Router. However, `retry()` is not allowed in Pages Router as it depends on `router.refresh()`, and will throw. Also, it's exported from `next/error` as there was already an `Error` component for the [Pages Router](https://nextjs.org/docs/pages/building-your-application/routing/custom-error#reusing-the-built-in-error-page). ### DevTools <img width="508" height="90" alt="CleanShot 2026-03-13 at 03 02 46@2x" src="https://github.com/user-attachments/assets/8b79b1f6-877d-4901-99f7-6a2b4d3e34fe" /> Docs to follow up: #89847 Closes NAR-768 --------- Co-authored-by: Josh Story <story@hey.com>
devjiwonchoi
force-pushed
the
jiwon/02-11-docs_catcherror_
branch
3 times, most recently
from
53d599a to
4b3e2a6
Compare
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4b3e2a68be
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
devjiwonchoi
force-pushed
the
jiwon/02-11-docs_catcherror_
branch
from
4b3e2a6 to
da78b91
Compare
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: da78b91edc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
devjiwonchoi
force-pushed
the
jiwon/02-11-docs_catcherror_
branch
from
da78b91 to
cd73cfe
Compare
|
@codex review |
|
Codex Review: Didn't find any major issues. More of your lovely PRs please. ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
3 participants
Docs for #89688