-
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
Gatsby build failing on netlify #6138
Comments
In your gatsby-node file, have you tried returning a promise with the graphql query? |
@krichdev I think I fixed this by upgrading specifically to the latest package in package.json. Now I'm having a different netfily error where it is saying that the build is timing out. Do you think what you suggest would help with that? |
I think it might. The Here is the gatsby blog example node file: |
Also do you see the same errors when you run |
Hey @m-allanson I updated the gatsby node and pushed again and still has the build fail errors. Perhaps its something to do with the amount of images I have for my posts? I don't show any errors when I run gatsby-build locally. |
How long does the build take locally? |
@KyleAMathews gatsby develop, when starting from scratch does take some time, though I haven't measured it. 15 minutes or so may be right. I think I read in another issue that the work around was to upload the build files instead of trying to build from github? |
Yeah, it sounds like you're hitting the Netlify build limit. Image processing does take a really long time is probably what's causing the trouble. The easiest way to get around the timeout issue is yeah, to build locally and push new updates to Netlify. |
Thanks @KyleAMathews! |
Summary
I'm new to gatsby and react but I've got my site prototype up and running locally. But when I try to deploy to netlify it keeps failing.
I've looked at previous issues which seemed to get around this by upgrading various plugins (#4996, #4990, #4989) but as far as I can tell, everything is updated.
I'm not sure what I'm messing up.
The final error is:
And before that there are lots of these errors:
Relevant information
Environment (if relevant)
System:
OS: macOS High Sierra 10.13.4
CPU: x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 9.6.1 - /usr/local/bin/node
npm: 3.10.7 - ~/.nvm/versions/node/v6.6.0/bin/npm
Browsers:
Chrome: 67.0.3396.87
Firefox: 60.0.2
Safari: 11.1
npmPackages:
gatsby: ^1.9.153 => 1.9.270
gatsby-image: ^1.0.54 => 1.0.54
gatsby-link: ^1.6.34 => 1.6.44
gatsby-paginate: ^1.0.16 => 1.0.16
gatsby-plugin-catch-links: ^1.0.24 => 1.0.24
gatsby-plugin-lodash: ^1.0.11 => 1.0.11
gatsby-plugin-netlify: ^1.0.21 => 1.0.21
gatsby-plugin-offline: ^1.0.18 => 1.0.18
gatsby-plugin-react-helmet: ^2.0.3 => 2.0.11
gatsby-plugin-react-next: ^1.0.11 => 1.0.11
gatsby-plugin-sass: ^1.0.26 => 1.0.26
gatsby-plugin-sharp: ^1.6.48 => 1.6.48
gatsby-plugin-typography: ^1.7.19 => 1.7.19
gatsby-remark-copy-linked-files: ^1.5.37 => 1.5.37
gatsby-remark-embed-video: ^1.4.0 => 1.4.0
gatsby-remark-images: ^1.5.67 => 1.5.67
gatsby-remark-katex: ^1.0.14 => 1.0.14
gatsby-remark-prismjs: ^2.0.4 => 2.0.4
gatsby-remark-responsive-iframe: ^1.4.20 => 1.4.20
gatsby-remark-responsive-image: ^1.0.0-alpha13-alpha.435e0178 => 1.0.0-alpha13-alpha.435e0178
gatsby-remark-smartypants: ^1.4.12 => 1.4.12
gatsby-source-filesystem: ^1.5.39 => 1.5.39
gatsby-transformer-remark: ^1.7.44 => 1.7.44
gatsby-transformer-sharp: ^1.6.27 => 1.6.27
npmGlobalPackages:
gatsby-cli: 1.1.58
File contents (if changed)
gatsby-config.js
:package.json
:gatsby-node.js
:gatsby-browser.js
: N/Agatsby-ssr.js
: N/AThe text was updated successfully, but these errors were encountered: