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.

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

Gatsby Develop Command Hangs on "Building development bundle" #69

Open
Stu1986c opened this issue Oct 16, 2019 · 3 comments
Open

Gatsby Develop Command Hangs on "Building development bundle" #69

Stu1986c opened this issue Oct 16, 2019 · 3 comments

Comments

@Stu1986c
Copy link

Stu1986c commented Oct 16, 2019

Hi

I run the prescribed steps to get Gatsby installed, run yarn and finally gatsby develop --open

On doing so, it prints the folllowing to the console:

image

It now just hangs at the Building development bundle stage.

I've searched everywhere for a fix but yet to find anything. I'm running Node Version: 12.4.0

Any ideas would be appreciated.

@Coder2012
Copy link

Coder2012 commented Dec 10, 2019

I also have an issue with Gatsby hanging, after just a clean clone and gatsby develop, I'm on Windows 10:

NOTE: The default Gatsby starter works fine

Tested on mac, get exactly same output including the error below but it runs fine in localhost:8000

PS C:\git\monzo\progression-framework> gatsby develop
success open and validate gatsby-configs - 0.040s
success load plugins - 14.848s
success onPreInit - 0.009s
success initialize cache - 0.028s
success copy gatsby files - 0.430s
success onPreBootstrap - 0.037s
success createSchemaCustomization - 0.014s
success source and transform nodes - 1.221s
success building schema - 1.343s
success createPages - 0.019s
warn Action createPage was called outside of its expected asynchronous lifecycle createPages in default-site-plugin.
Ensure that you return a Promise from createPages and are awaiting any asynchronous method invocations (like graphql or http requests).
For more info and debugging tips: see https://gatsby.dev/sync-actions

File C:\git\monzo\progression-framework\gatsby-node.js:46:7
  44 |     }
  45 |     result.data.allMarkdownRemark.edges.forEach(({ node }) => {
> 46 |       createPage({
     |       ^
  47 |         path: node.frontmatter.path,
  48 |         component: FrameworkView,
  49 |         context: {
success createPagesStatefully - 0.286s
success onPreExtractQueries - 0.009s
success update schema - 0.031s   
success extract queries from components - 0.303s
success write out requires - 0.080s
success write out redirect data - 0.023s
warn The icon(src/images/favicon.png) you provided to 'gatsby-plugin-manifest' is not square.        
The icons we generate will be square and for the best results we recommend you provide a square icon.

success Build manifest and related icons - 0.218s
success onPostBootstrap - 0.572s
⠀
info bootstrap finished - 33.412 s
⠀
success run queries - 0.366s - 21/21 57.37/s

 ERROR 

Warning: React version not specified in eslint-plugin-react settings. See https://github.com/yannickcr/eslint-plugin-react#configuration .

⠋ Building development bundle

@szopkap
Copy link

szopkap commented Dec 13, 2019

There are two problems:

  "settings": {
    "react": {
      "version": "detect"
    }
  },
  • There is a plugin eslint-plugin-flowtype-errors (https://www.npmjs.com/package/eslint-plugin-flowtype-errors) and this plugin stucks the build process. I updated the version number to the latest release (4.1.0) (plus I updated the eslint-plugin-react version number too) and the dev build process runs fine (but a little bit slowly).
    • Also you can choose to remove this plugin (and remove the config from the .eslintrc), if you want a faster dev build process :).

@Coder2012
Copy link

@szopkap Thank you for the suggestions and glad it works for you.

I also updated the react version as you suggested, and updated the eslint-plugin-flowtype-errors to 4.1.0 it appears to hang but just takes a while and it does build development build just fine.

Thank you very much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants