From 58bd72425343c6d74d097c816a1cd8b8b0ad9138 Mon Sep 17 00:00:00 2001 From: Shu Ding Date: Mon, 31 Oct 2022 09:34:32 -0700 Subject: [PATCH] Update errors/invalid-segment-export.md Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com> --- errors/invalid-segment-export.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/errors/invalid-segment-export.md b/errors/invalid-segment-export.md index c9d9aeba8ab815e..34b046edb26898c 100644 --- a/errors/invalid-segment-export.md +++ b/errors/invalid-segment-export.md @@ -2,7 +2,7 @@ #### Why This Error Occurred -Your [layout](https://beta.nextjs.org/docs/api-reference/file-conventions/layout) or [page](https://beta.nextjs.org/docs/api-reference/file-conventions/page) inside the app directory exports an invalid field. In these files, it’s only allowed to export a default component, or Next.js configuration options for layout and pages, such as `revalidate`, `generateStaticParams`, etc. +Your [layout](https://beta.nextjs.org/docs/api-reference/file-conventions/layout) or [page](https://beta.nextjs.org/docs/api-reference/file-conventions/page) inside the app directory exports an invalid field. In these files, you're only allowed to export a default React component, or [Segment Configuration Options](https://beta.nextjs.org/docs/api-reference/segment-config) for layout and pages, such as `revalidate`, `generateStaticParams`, etc. Other custom export fields are not allowed to avoid typos, as well as using names that can be used as new options by Next.js in the future.