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

merged 2 commits into from Feb 14, 2022

Commits on Feb 14, 2022

  1. docs: Add link to pageExtensions config in page-without-valid-compone… 

    …nt.md

The [Page Without Valid React Component](https://nextjs.org/docs/messages/page-without-valid-component) explains some ways to fix the problem of Next finding a non-React Component. However, if someone is trying to use `.mdx` as an extension, or wants to include tests, stories or other non-page files in their `pages` folder there's nothing for them.

The [Custom Page Extensions](https://nextjs.org/docs/api-reference/next.config.js/custom-page-extensions) has all the info to help them out, but adding it to this error page should make it more discoverable.
    @benmvp
    benmvp committed Feb 14, 2022
    Configuration menu
    Copy the full SHA
    17952ee View commit details
    Browse the repository at this point in the history

  2. Merge branch 'canary' into patch-1

    @ijjk
    ijjk committed Feb 14, 2022
    Configuration menu
    Copy the full SHA
    df23222 View commit details
    Browse the repository at this point in the history