-
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
Errors on first install (childImageSharp/gatsby-transformer-sharp) #9511
Comments
@cmkshaw If you are still getting the above error, that might be an installation of Did you had a chance to look at image-processing example which showcases the use of |
Hello! I haven't looked at the plugin examples, because I haven't gotten that far yet... I just want to install plain ol' Gatsby 😅 I suppose I'm confused why I'm getting these issues on first install -- if there are plugins to be installed alongside Gatsby, shouldn't those be included in the very detailed setup guide? |
I'm having the same issue with v2.0.7, but still works with v2.0.5 You can try it with:
|
@mgrubinger yikes! Did you mean |
@DSchau In my case it was related to gatsby-transform-manifest Here's the error message:
However, I could not create a reproduceable setup in a new project. It seems my problem was related to this issue: #8852 I saw the message about the cached libvips after installation of After removing the cached zip AND upgrading to Sorry for the confusion, I should have tried to upgrade |
Using v2.0.5 works for me, thanks @mgrubinger. |
@cmkshaw @mgrubinger I'm not getting any errors when using Environment info:
|
I just got the exact same error when grabbing gatsby-cli 2.44 using yarn. OS: Manjaro 18.0 |
@miyagui from my experience with linux and gatsby, there's a need of the equivalent of build-essentials package for the distribution you're using and also python. This circumvents/fixes some issues experienced with plugin gatsby-plugin-sharp and nodegyp. |
This is happening for me too. Here is my Environment info:
|
still working on my solution but I think it may have to do with Python3 being the default version. Gatsby doesn't support Python3 (EDIT: actually not Gatsby, but EDIT: can confirm it was python 3 being called by node. Removing my (Anaconda-inserted) conda profile code from my .bash_profile allowed me to successfully |
@TristanTheKnightAway it's not actually gatsby fault,the issue lies with nodegyp, which is used by some of components/plugins, namely gatsby-plugin-sharp and as you can see here as it does not work with python 3. This is one of the situations that's outside the control of gatsby |
hey thanks @jonniebigodes for the comment and clarification. Wasn't trying to place blame on Gatsby, just trying to finger my specific issue. Helpful to know it's a node thing. I ran across a lot of open-ended error threads that didn't mention python so figured it was worth a mention here for someone else. I thought it strange when I saw a python fail somewhere down the line of blood red error messages and I'm super happy it turned out to be the culprit. I bet if I went to the Gatsby docs it's probably mentioned there... |
@TristanTheKnightAway when i read your comment i understood where you were going and i was picking up on what i've said and expanding it a bit, so that this particular issue you were experiencing and for people that can be affect by this also, could pinpoint on the solution faster. Hope to see some content of yours in here in the near future 👍 |
This adds Python to output of `gatsby info` `gatsby-plugin-sharp` is very widely used and is included in the default starter. `sharp` uses `nodegyp` which needs `python` and according to its documentation > v2.7 recommended, v3.x.x is not supported We've seen several issues where building breaks due to `sharp` not working like #10620 and #9511 Knowing the python version in the env helps in these cases
I just started using Gatsby and I can confirm I have this exact same issue, however my Python is at 2.7 so I'm not sure if that's the cause in my case. I followed what another dev did in this issue #8148 and lo and behold it worked which makes it appear that there is some plugin issue. I just did:
Then deleted |
I had this same issue using Gatsby |
Unfortunately none of the above are working for me, have replicated all of your above version combos to no avail. Figures this happens on the one afternoon I've allocated to play around with this, haha. EDIT: Reverted back to python 2.7 and did this Lovely day to you all. |
This adds Python to output of `gatsby info` `gatsby-plugin-sharp` is very widely used and is included in the default starter. `sharp` uses `nodegyp` which needs `python` and according to its documentation > v2.7 recommended, v3.x.x is not supported We've seen several issues where building breaks due to `sharp` not working like gatsbyjs#10620 and gatsbyjs#9511 Knowing the python version in the env helps in these cases
Gatsby |
Also running into this issue with the latest Gatsby 2.0.116 |
Been through this issue of creating new Gatsby project, I would say follow the latest installing instructions by Gatsby docs. Use
But if you successfully build the project and are using Windows OS, and you try to build development version of the project using My piece of advice (actually advice originally given by gatsby team itself) is to use Ubuntu Windows Subsystem for Linux(WSL). You can install it for free from Microsoft store. Check out this link: https://www.gatsbyjs.org/docs/gatsby-on-windows/ You'll find at the very bottom of the page their recommendation to use WSL to install node modules. Just follow them and you'll find your gatsby project gets built without any issues. And of course, you can then do I hope this helps! |
I got the same issue with the first install and similar with the blog starter (Mac, node 11.11). What helped (BTW I don't know why I did it, lol) - I looked what commands CLI has and tried 'clean' - and magic. |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! Thanks for being a part of the Gatsby community! 💪💜 |
I was having this problem today - just opened up an old project and |
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m Thanks again for being part of the Gatsby community! |
Hi! I did a quick command-F for
childImageSharp
/gatsby-transformer-sharp
in existing issues but didn't see anything for first-time installers at a glance.Description
I've followed the first three steps of your setup guide and am stalled with errors.
Steps to reproduce
Ran:
npm install --global gatsby-cli
gatsby new gatsby-site https://github.com/gatsbyjs/gatsby-starter-default
cd gatsby-site
gatsby develop
Expected result
Gatsby will start a hot-reloading development environment accessible at localhost:8000
Actual result
... stuff
Multiple instances of:
finally,
Environment
The text was updated successfully, but these errors were encountered: