gatsby: Cannot build locally after upgrade
Description
Having not worked on a client project for a few months I jumped back in for site updates, upgrading a few dependencies as instructed as well as gatsby 2.7.19 to 2.15.28.
After trying to rebuild locally after the updates I have been unsuccessful for a few hours, with the site getting stuck on the source and transform nodes
process within gatsby-source-prismic
when trying to download images for the news page of the site. No matter what I try, the site will not build locally.
I noticed that gatsby-source-prismic
migrated to a new version of the API (v3), however applying these updates didn’t do anything, so I have reverted to the previous version.
After pushing my updates to github I have noticed that netlify persists with processing the images and builds the site, however it now takes 19 minutes to publish the site, rather than 3 minutes in previous successful build before any updates.
A few things to note…
-
This is a related issue to https://github.com/angeloashmore/gatsby-source-prismic/issues/73 however the usual suggestions of “resizing the terminal” or “restarting” don’t work.
-
I had previously encountered and resolved the same issue within netlify (didn’t occur locally) when pushing to build by using https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-netlify
Thank you in advance for any help, this was my first gatsby site and I am still figuring a lot out!
Steps to reproduce
run gatsby-develop on latest deployment
You can see the project at : https://github.com/immbudden/Lanyon
Expected result
Site should generate all news images using childImageSharp and static site should be rendered
Actual result
Firstly, after all of the updates, I get the below error, which I think is unrelated but am not sure…
ERROR
(node:40989) ExperimentalWarning: The WHATWG Encoding Standard implementation is an experimental API. It should not yet be used in production applications.
Then after gatsby begins to query files from prismic…
source and transform nodes
hangs around the 95% mark.
Environment
Run gatsby info --clipboard
in your project directory and paste the output here.
System: OS: macOS 10.14.3 CPU: (8) x64 Intel® Core™ i7-6700HQ CPU @ 2.60GHz Shell: 3.2.57 - /bin/bash Binaries: Node: 8.6.0 - ~/.nvm/versions/node/v8.6.0/bin/node Yarn: 1.12.3 - /usr/local/bin/yarn npm: 6.9.0 - ~/.nvm/versions/node/v8.6.0/bin/npm Languages: Python: 2.7.10 - /usr/bin/python Browsers: Chrome: 77.0.3865.90 Safari: 12.0.3 npmPackages: gatsby: ^2.3.17 => 2.15.28 gatsby-image: ^2.0.0-rc.4 => 2.2.23 gatsby-paginate: ^1.0.17 => 1.1.1 gatsby-plugin-emotion: ^3.0.1 => 3.0.1 gatsby-plugin-favicon: ^3.1.5 => 3.1.6 gatsby-plugin-google-analytics: ^2.0.17 => 2.1.19 gatsby-plugin-netlify-cache: ^1.1.0 => 1.2.0 gatsby-plugin-react-helmet: ^3.0.12 => 3.1.10 gatsby-plugin-robots-txt: ^1.4.0 => 1.5.0 gatsby-plugin-sharp: ^2.0.33 => 2.2.27 gatsby-plugin-sitemap: ^2.1.0 => 2.2.16 gatsby-plugin-styled-components: ^3.0.4 => 3.1.8 gatsby-plugin-typography: ^2.2.2 => 2.3.10 gatsby-remark-responsive-iframe: ^2.0.8 => 2.2.20 gatsby-source-filesystem: ^2.0.25 => 2.1.28 gatsby-source-prismic: ^2.2.0 => 2.2.0 gatsby-transformer-remark: ^2.1.15 => 2.6.26 gatsby-transformer-sharp: ^2.1.9 => 2.2.19 npmGlobalPackages: gatsby-cli: 2.7.53
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 25 (13 by maintainers)
Here’s something interesting https://spectrum.chat/gatsby-js/general/dyld-lazy-symbol-binding-failed-symbol-not-found~eef6ba21-b37e-4b36-88ec-0b321ed11475
How odd.
Just wanted to drop a cleaned up copy of the log. Gatsby-issues-17940.txt