-
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
Error when running gatsby new gatsby-site; abrupt ending of installation #8852
Comments
Looks like the cached zip is broken. Does it work after rm /home/geeky_srm/.npm/_libvips/libvips-8.6.1-linux-x64.tar.gz |
That did the trick! |
I have the same error (for the same Ubuntu Bionic), and doing @stefanprobst's |
It worked after I |
I'm still experiencing this issue on my Mac Gatsby CLI version: 2.8.5 I experience it when i follow your video tutorial (https://www.gatsbyjs.org/docs/quick-start) suggesting but not when I execute Does your video need to be updated? |
Also experiencing it now, i have been sturggling on this for days. Here is what i got when excute error /mnt/d/iot.docs.new/iot-docs-beta/node_modules/sharp: Command failed. |
Hi, I was having this same problem in a fresh ubuntu install, I tried Installing the build essential package, but nothing seems to work, but I figure it out to install python 2.7 and after that, the problem was solved. |
Description
I tried to run the command
gatsby new gatsby-site
.But I am presented with this error:
Steps to reproduce
Running
gatsby new gatsby-site
Expected result
The new gatsby site would have been created
Actual result
Abrupt error.
Environment
System:
OS: Linux 4.15 Ubuntu 18.04.1 LTS (Bionic Beaver)
CPU: x64 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
Shell: 4.4.19 - /bin/bash
Binaries:
Node: 10.7.0 - ~/.nvm/versions/node/v10.7.0/bin/node
Yarn: 1.10.1 - /usr/bin/yarn
npm: 6.4.1 - ~/.nvm/versions/node/v10.7.0/bin/npm
Browsers:
Chrome: (47ead77cb35ad2a9a83248b292151462a66cd881)
Firefox: 62.0.3
npmGlobalPackages:
gatsby-cli: 2.4.2
gatsby: 2.0.12
The text was updated successfully, but these errors were encountered: