Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: Add link to pageExtensions config in page-without-valid-component.md #34285

Merged
merged 2 commits into from Feb 14, 2022
Merged

docs: Add link to pageExtensions config in page-without-valid-component.md #34285

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
17952ee
docs: Add link to pageExtensions config in page-without-valid-compone…
benmvp Feb 13, 2022
df23222
Merge branch 'canary' into patch-1
ijjk Feb 14, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 2 additions & 0 deletions errors/page-without-valid-component.md
View file
Open in desktop
Expand Up @@ -14,3 +14,5 @@ For each, you'll want to check if the file is meant to be a page.
If the file is not meant to be a page, and instead, is a shared component or file, move the file to a different folder like `components` or `lib`.

If the file is meant to be a page, double check you have an `export default` with the React Component instead of an `export`. If you're already using `export default`, make sure the returned value is a valid React Component.

If you need to support a different file extension for a page component (such as `.mdx`) or would like to include non-page files in the `pages` directory, configure [Custom Page Extensions](https://nextjs.org/docs/api-reference/next.config.js/custom-page-extensions) in the `next.config.js`.