-
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
Cannot setup Gatsby Default Starter #13780
Comments
Well this is unfortunate! We use slightly older versions of So, two solutions here:
Sorry for the frustration here--thanks! |
And a 3rd solution from @pieh if a yarn user. Use the {
"resolutions": {
"sharp": "0.22.1"
}
} |
Thank you @DSchau for your quick reply. I've setup NVM to managing multiple Node versions. Now using the latest LTS-Version of Node and everything works fine. |
Just want to mention that I attempted this to resolve this issue for myself and was able to successfully
Preventing me from building and developing locally 😢 |
Description
I am trying to setup a new Gatsby project using the default starter template, following the associated documentation. This is the error I'm getting:
I already tried a couple of things I found here and on other forums concerning similar issues. What I need to mention is, that I am able to setup gatsby-starter-hello-world without any problems. This problems occurs with gatsby-starter-default and gatsby-starter-blog.
I reinstalled Node entirely from scratch via Homebrew and installed the Gatsby-CLI globally new as well. Furthermore I checked my XCode-Installation and can not see any issues with that.
An other user on Stackoverflow reported a very similar issue to mine a couple of hours ago, which you can find here.
Steps to reproduce
Following the commands from the Quick Start Guide.
Expected result
Gatsby project is setup properly and gatsby develop is starting the development environment under
localhost:8000
Actual result
Executing
gatsby new <my-gatsby-site>
results in the error shown above.Environment
The text was updated successfully, but these errors were encountered: