-
Notifications
You must be signed in to change notification settings - Fork 97
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
npm run build throws error : Generating JavaScript bundles failed #69
Comments
Gatsby 2.0 beta is live, I need to update all this starter. For now we have some weird compilation fails and I don't really know why… sometime is working sometime not, and it's really hard to debug (because of course, on my computer, it's working). Really sorry for this bunch of errors, I really need to re-work a bit on this project, but I also have a lot to do aside… Time is always the issue ^^ Regarding you logs, it's somewhere in Typescript, you can begin by allow implicit any 😉 |
@fabien0102 Personally I like semantic-ui & react & typescript and using Gatsby 2, i have gone through the upgrade procedure here, at a heavily personalized fork. I did not have time to remove the personalization from the blog, sorry. But even that should help you quickly update the starter. However,with Gatsby 2 there are some issues with image processing. I am not so familiar with Gatsby therefore could not figure out what causes the issues with graphql image processing. ImageSharp responsiveResolution appears not to be available anymore, correct? Any suggestions in that regard? Thanks in advance! |
I have later discovered that there was a "next" branch for the upgrade. 👍 build is fine with that branch. There was only one thing i had to fix: in blogs.tsx instead of because sometimes avatars are childImageSharp Now it builds fine and works very well with gatsby 2. |
Have tried all the workarounds. Nothing seems to be working.
If i update my node version to 9.10.1, my sharp compatibility goes for a toss as they haven't come up with a sharp package which is compatible with node version 9.10.1.
The text was updated successfully, but these errors were encountered: