-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
TypeError: Cannot read property 'componentChunkName' of undefined #12725
Comments
After starting |
I have the same issue on hot reload, any chance you're using Removing |
I have this, maybe some of the plugins use
|
I am seeing this as well, I haven't tried installing But I have a question for everyone. When you do |
that issue was fixed in recent 2.2.4 gatsby build, try to update gatsby itself, not cli |
@sarahannnicholson This shouldn't occur when running @AAverin Can you link to a minimal reproduction of this if possible? |
#12671 this pull fixes pages deletion (even 404) in development mode, its live in version 2.2.4 |
I'll update and keep testing, thanks |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! Thanks for being a part of the Gatsby community! 💪💜 |
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m Thanks again for being part of the Gatsby community! |
Description
After implementing some generated pages (blog posts) often dev version of Gatsby breaks with
TypeError: Cannot read property 'componentChunkName' of undefined
Only restarting
gatsby develop
solves the problemSteps to reproduce
Not sure what was the cause and how to cleanly reproduce it. I assume that generating pages using
createPages
,onCreateNode
andonCreatePages
might be the cause of the problem.Environment
System:
OS: macOS High Sierra 10.13.6
CPU: x64 Intel(R) Core(TM) i7-7920HQ CPU @ 3.10GHz
Shell: 5.3 - /bin/zsh
Binaries:
Node: 10.10.0 - /usr/local/bin/node
npm: 6.4.1 - /usr/local/bin/npm
Browsers:
Chrome: 73.0.3683.86
Safari: 11.1.2
npmGlobalPackages:
gatsby-cli: 2.4.4
The text was updated successfully, but these errors were encountered: