Unverified Commit 63651a63 authored by Faris Masad's avatar Faris Masad Committed by GitHub

Add note about using the /_error page directly to custom error page article (#39671)

See https://github.com/vercel/next.js/issues/39144

It's not completely clear that `/_error` should not be used as a normal page. Added a note under `Caveats` in the custom error page article
parent b7c2bd10
......@@ -98,3 +98,4 @@ If you have a custom `Error` component be sure to import that one instead. `next
### Caveats
- `Error` does not currently support Next.js [Data Fetching methods](/docs/basic-features/data-fetching.md) like [`getStaticProps`](/docs/basic-features/data-fetching/get-static-props.md) or [`getServerSideProps`](/docs/basic-features/data-fetching/get-server-side-props.md).
- `_error`, like `_app`, is a reserved pathname. `_error` is used to define the customized layouts and behaviors of the error pages. `/_error` will render 404 when accessed directly via [routing](/docs/routing/introduction) or rendering in a [custom server](/docs/advanced-features/custom-server).
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment