-
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
gatsby new fails with starter: node-gyp rebuild fails #4121
Comments
Hang on! Please don't spend any time on this issue just yet; I don't have g++ installed. Let me work out of for now; understand why and I'll update this thread and docs (better specification in pre-requisites I imagine). |
brainwipe
added a commit
to brainwipe/gatsby
that referenced
this issue
Feb 19, 2018
When running `npm install` on a starter that uses native npm extensions via `node-gyp`, the user needs to know that they need `build-essentials`. A clean Ubuntu xenial install won't have it by default. Closes gatsbyjs#4121
This was referenced Jan 12, 2022
This was referenced Mar 20, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When running gatsby new on the gatsby-material-starter, sharp fails.
Environment
Gatsby version: 1.1.40
Node.js version: 9.5.0
Operating System: Ubuntu 16.04.2 xenial LTS running as admin rights on the Windows Subsystem. x64 with node running as x64.
Actual result
Note, I did manage to get a gatsby new site (empty) running. It appears to be some of the dependencies that are failing.
Expected behavior
I get a new site.
Steps to reproduce
1. Follow gatsby tutorial 1
2. Type gatsby new icar2 https://github.com/Vagr9K/gatsby-material-starter into console.
Thank you!
The text was updated successfully, but these errors were encountered: