Getting error when running gatsby build!
See original GitHub issueRunning gatsby build throws following error:
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
not finished createPagesStatefully - 0.079s
Could be due to one of the plugins versions, tried solving locally but couldn’t get it!
gatsby develop gives below errors in browser:
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Troubleshooting Common Errors - Gatsby
Error : ReferenceError: window is not defined when running gatsby build; Build problems from Field 'browser' doesn't contain a valid alias configuration ...
Read more >gatsby develop ok, but gatsby build failed · Issue #3425 - GitHub
To create a production build, use gatsby build WAIT Compiling. ... Due to the high number of incoming GitHub issues, we have to...
Read more >Why my gatsby build failed on Error: ENOENT: no such file or ...
try deleting the .cache directory in your gatsby project and run yarn start or yarn build again (or the equivalent npm commands if...
Read more >Gatsby run build - error at createPages that is working ok on ...
Hi, my site name is : sleepy-rosalind-fabd9f. I'm having errors at building stage - on develop stage it works fine - according the...
Read more >Gatsby Cloud build error - Developing with Prismic
It might be that you need to clear the cache of your project. Clear the cache, and re-build your project. Let me know...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ederst @itzsrv
I published a new version of Chronoblog - v0.23.0 (https://www.npmjs.com/package/gatsby-theme-chronoblog).
It would be great if you tested the new version. The problems listed here, I hope, have been resolved, but I’m not 100% sure.
@Ganevru can confirm that it’s working now wit
npm
too; tested withgit clone; npm i
, and withgatsby new
thanks!