-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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.
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
ERROR #11328 A page component must export a React component for it to be valid. Please make sure this file exports a React component: undefined #1516
Comments
I found that this may caused by the update of gatsby, when I use yarn's resolutions to set gatsby@2.22.15, this error no longer exists. |
Same Issue. @roland-reed's workaround worked fine. |
Also started getting this issue. Yarn resolution fixed it for me as well. |
same issue. I think the root cause of this issue is mdx v2 of gatsbyjs. |
same issue. I agree with @nguyenletan. |
Upgrade gatsby to latest version will slove it. |
I have to reopen this issue, same problem in |
@roland-reed You closed the issue, what did you do to solve it? |
|
i Have the same Error System: |
Bug Report
Describe the bug
ERROR #11328
A page component must export a React component for it to be valid. Please make sure this file exports a React component:
undefined
This error is thrown when I'm trying the Gatsby Remark VSCode with Docz
To Reproduce
Following the guide will lead to the problem:
Expected behavior
No error
Environment
Additional context/Screenshots
Add any other context about the problem here. If applicable, add screenshots to help explain.
The text was updated successfully, but these errors were encountered: