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
Deploying to Netlify Stuck #15205
Comments
Same issue here. My site builds eventually but looks terrible. Seems to be styled components not building correctly. |
Yeah same issue for me, haven't touched any files since the last deploy |
+1 @i-bsd I'm experience build failure after adding styled-components/gatsby-plugin-styled-components |
I was having a similar issue with my builds failing out of no where but managed to fix my issues by disabling source maps using this gatsby plugin. I'm not totally sure why this worked for me. |
Build stuck for me locally after adding Gatsby styled components plugin. It was fine without the plugin. I have figured out that this was the culprit:
So to fix the issue I had to do this:
Looking at its release history I figure that the issue appeared between 1.10.1 and 1.10.4. Considering this thread started 2 days ago, I suspect 1.10.2 released 6 days ago wasn't the issue. 1.10.4 was a minor change released in the same day, so not likely the issue. Here's a list of changes:
I invite you to further investigation. |
Looking at the list of issues I found that gatsby users weren't the only victims: |
Tried a combo of all of these but sadly still stuck. Think we all have a same same but different issue depending on the various packages we have installed. |
For me, I disabled |
I am still having this issue. I've tried the above fixes adding no sourcemaps and also disabling react-lazyload. Gatsby build and develop both complete locally. Netlify is stuck. |
@rkretch91 @ArthurHwang Have you tried installing a different version of babel-plugin-styled-components? |
Looks like it's fixed in babel-plugin-styled-components@1.10.6 |
I my case I couldn't solve it with Style Components upgrade or leaving out Source Maps. I documented it over here, because for me it is related to MDX ChristopherBiscardi/gatsby-mdx#411 |
Yes 1.10.6 finally worked for me! Still trying to figure out what happened here, but I am happily deployed again :) Thanks @Vanuan for the fix. |
we've done a few fixes on gatsby@2.11.8 so that should work. If not, please let us know. |
Summary
Deploying to Netlify gets stuck after
[BABEL] Note: The code generator has deoptimised the styling of /opt/build/repo/node_modules/react-intl/locale-data/index.js as it exceeds the max of 500KB.
Relevant information
After running a successful
gatsby build
andgatsby serve
on my project https://github.com/rkretch91/wc, I then try to deploy to Netlify and it pauses on the following line of code for a long time before timing out 15 or 20 minutes later[BABEL] Note: The code generator has deoptimised the styling of /opt/build/repo/node_modules/react-intl/locale-data/index.js as it exceeds the max of 500KB.
I haven't touched any of the root files since the last successful deploy. The only thing I altered slightly was some styling and functionality on my map component (mapbox) and like I said, the local build was successful.
Cannot find an issue that is exactly related here.
Environment (if relevant)
Netlify Deploy Log
The text was updated successfully, but these errors were encountered: