mirror of
https://github.com/hanzoai/next.js.git
synced 2026-09-24 17:00:51 +00:00
Jiwon ChoiandGitHub
74ce6b2e2f
### What? Reverts #94617, which had reverted #94610. This re-lands the stabilization of the `catchError` API and the `retry` error prop by removing their `unstable_` prefix across source, docs, and tests. ### Why? #94610 was reverted in #94617 to unblock another change. This re-applies it now that it is no longer blocked. ### How? `git revert` of the revert commit. The repo's custom errors.json merge driver handled the error registry: the original codes `1324`/`1325` had been reclaimed by `instant` errors after the revert, so the reintroduced messages were minted as new codes `1360` (`retry()` can only be used in the App Router) and `1361` (`catchError` can only be used in Client Components), keeping errors.json append-only. The docs changelog adds `v16.3.0 | catchError became stable.` while retaining the historical `v16.2.0 | unstable_catchError introduced.` row. ### Verification - `pnpm update-error-codes` (check_error_codes passes; errors.json in sync) - `pnpm build` (full JS build, exit 0) - `pnpm --filter=next types` (exit 0) - Not run: Rust/cargo build (`react_server_components.rs` change is a one-line allow-list string revert; left to CI) <!-- NEXT_JS_LLM_PR -->
25 lines
554 B
TypeScript
25 lines
554 B
TypeScript
'use client'
|
|
|
|
import type { ErrorInfo } from 'next/error'
|
|
import { catchError } from 'next/error'
|
|
|
|
export function ErrorFallback(
|
|
props: { title: string },
|
|
{ error, reset, retry }: ErrorInfo
|
|
) {
|
|
return (
|
|
<>
|
|
<p id="error-boundary-message">{(error as Error).message}</p>
|
|
<p id="error-boundary-title">{props.title}</p>
|
|
<button id="reset" onClick={() => reset()}>
|
|
Reset
|
|
</button>
|
|
<button id="retry" onClick={() => retry()}>
|
|
Retry
|
|
</button>
|
|
</>
|
|
)
|
|
}
|
|
|
|
export default catchError(ErrorFallback)
|