Closed anneramey closed 4 years ago
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! As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!
Thanks for being a part of the Gatsby community! πͺπ
I have this issue as well.
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! As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!
Thanks for being a part of the Gatsby community! πͺπ
Hi!
If things I private, you can always reach out on ward@gatsbyjs.com
Sorry to hear you're running into an issue. To help us best begin debugging the underlying cause, it is incredibly helpful if you're able to create a minimal reproduction. This is a simplified example of the issue that makes it clear and obvious what the issue is and how we can begin to debug it.
If you're up for it, we'd very much appreciate if you could provide a minimal reproduction and we'll be able to take another look.
Thanks for using Gatsby! π
Closed due to lack of reproduction.
I'm having issues with this exact problem except its 100% of the time. I might have to abandon this plugin. Wish there was a fix.
I am having this issue on mac, 100 % of the time. From what I found, there seems to be many reasons why this can happen. Someone even recommended resizing the terminal window, which fixed the issue for some.
Have you at least found any way to debug this better?
I was running into this too but remembered I had just allowed eslint to fix a bunch of syntax problems in gatsby-node.js that it apparently didn't like. I'm afraid to go in there again and test which exact "fix" created the problem but reverting the changes seems to have cleared the blockage. For now.
Summary
About 60% of the time, when I locally do a gatsby build or gatsby develop, the build gets hung on createPages
Relevant information
This happens with complete inconsistency. It will happen many times in a row or not for days. Clearing the cache and public folders doesn't seem to help. This is for my contentful site. Not sure what I'm doing wrong. I'm on windows 10. My mac coworker doesn't have the issue. This has been happening through several versions of the gatsby-cli
success open and validate gatsby-configs - 0.086s success load plugins - 4.133s success onPreInit - 0.020s success delete html and css files from previous builds - 0.021s success initialize cache - 0.208s success copy gatsby files - 0.192s success onPreBootstrap - 2.194s success createSchemaCustomization - 0.058s Starting to fetch data from Contentful Fetching default locale default locale is : en-US contentTypes fetched 17 Updated entries 1284 Deleted entries 0 Updated assets 1008 Deleted assets 0 Fetch Contentful data: 10515.927ms success source and transform nodes - 13.332s success building schema - 1.379s warn code block or inline code language not specified in markdown. applying generic code block β ΄ createPages
Environment (if relevant)
File contents (if changed)
gatsby-config.js
:package.json
:gatsby-node.js
:gatsby-browser.js
:gatsby-ssr.js
: N/A