-
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
Failed at the sharp@0.21.0 install script. on ubuntu 16.04 #11026
Comments
Getting the exact same |
Getting the same when doploying with Now:
|
Getting the same, ubuntu 18.10
|
I was able to install on another machine with the same OS. Any idea what I might be missing on the machine that doesn't work? |
same issue |
What version of sharp is installed? There are probably 2 issues here EACCESS is mostly caused by wrong permissions on a folder or bad node installation. You could also try the following: (only applies to WSL, osx or linux)
now.sh:
It could be that now.sh doesn't allow installation of sharp. |
The issue in my case seemed to be related to npm. I have reinstalled node and npm and everything works fine. |
Same with me. Installed it on a VM and it works there. But on my machine not. UPDATE: Now it seems to work. After @wardpeet suggestion. I have no idea why. |
Thanks for your reply. Removing Nevertheless I tried the same extensively before submitting this issue and it did not work back then. Strange. Maybe someone fixed something in some package. |
I did all the steps outlined here. Reinstalled node, messed with permissions, deleted node_modules and package.json. I wasn't able to get it working until I finally deleted the project and re-cloned it from github. works now :) |
There was something strange. Did the same a week ago. It did not work. Yesterday I only deleted the node_modules folder and reinstalled them and it just worked. |
I managed to resolve this issue. If that doesn't work for you, I resolved the issue by installing node 8.14 (I'm not sure if this part is totally necessary, but this is how I got it to work) by doing: Let me know if it helped you! |
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! 💪💜 |
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! |
Never |
I just had the same issue and I could resolve it by installing sharp first: That it does it installs the newer version of sharp and it seems to solving the problem. |
The same for me, W10 and NodeJS v12.6.0, yarn gave the sharp error (with my repo, cloned in a new computer) I've gone to NodeJS v10.16.0 and yarn has succeeded, and everything works |
@kuworking is right. it's not working with v |
I don't really like jumping into issues that are marked closed but, given I found this when searching for an answer to my problem, it makes sense to. I'm on Windows 10, using NodeJS v12.6 and npm 6.9.0, and had sharp failing to work or install. Deleting the |
Same here @IrregularShed, I picked up a Gatsby site I hadn't touched for a while and ran into the issue. Removing |
@robinmetral Great, I'll give that a go when I get a chance |
None of the suggestions above worked for me (yarn, OS X, node 12.9.1) except for downgrading to Node 10, cleaning the yarn cache, rmving node_modules, running yarn install Annoying having to downgrade my node version for some image processing functionality I don't even use, but better than nothing I guess. |
Same here, I have to set Node to 10.17.0 in Gitlab CI pipeline otherwise I can't build.... :( |
you should download the libvips tar package manually, then put it into a folder named “_libvips” which you should found it in global cache folder. Then you can try another install ,and it works! |
yarn work for me too! |
nothing's working for me. |
same issue building Gatsby site (Mac M1). This worked: |
@rickschmoo Tried all this in Mac M1
|
I'm having this same issue trying to upgrade a site, any guidance would be greatly appreciated. |
@rickschmoo @twobitEDD |
Yes, I was able to do the following steps and was able to build:
https://geedew.com/What-does-unsafe-perm-in-npm-actually-do/ I'm still not sure why this happened... |
Same issue form me on M1 mac with |
Description
I am using
"gatsby-plugin-sharp": "^2.0.17",
as well as"gatsby-transformer-sharp": "^2.1.3"
. After installing, it seems that there is an issue installing the sharp dependency.Steps to reproduce
Expected result
Everything installed properly.
Actual result
Environment
UPDATE:
Before submitting this issue I tried extensively nearly everything, including removing
node_modules
andnpm install
everything again. It didn't work.After waiting a week I tried after @wardpeet suggestion removing
node_modules
andnpm install
everything again. Now ot works. I have no clue why or what did not work a week ago. Maybe an package update?The text was updated successfully, but these errors were encountered: