-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Regression: installation fails when space in path #2777
Comments
Hi, does the |
The |
I'm not sure if this helps, but I'm able to install it globally with |
I figured it out! The issue is that I'm developing on an iCloud folder. So clang can't find the path starting with Definitely keeping active development out of cloud folders from now on. |
I think this is to do with the space in the path as the Previously a work-around was added to sharp via commit da0dc28 but a more recent commit fbdac80 appears to have regressed the behaviour. I'd like to reopen this issue so we can use it to track getting the workaround added back in again. |
Should be fixed via commit 95431bd and will be part of v0.29.0 - thanks for reporting this. |
v0.29.0 now available. |
I'm having issues installing any npm modules that use sharp. I tried installing sharp on its own, and run into the same issues. I'm using an M1 Mac. I have also tried using the globally installed vips via brew, but that didn't work, nor do I think it should be necessary. I've looked through all the existing issues and haven't been able to pinpoint why it's not installing. I appreciate any help!
The most relevant part of the output appears to me to be:
Answered questions:
Did you see the documentation relating to installation?
Yes
Have you ensured the architecture and platform of Node.js used for
npm install
is the same as the architecture and platform of Node.js used at runtime?Yes
Are you using the latest version? Is the version currently in use as reported by
npm ls sharp
the same as the latest version as reported bynpm view sharp dist-tags.latest
?Yes
If you are using npm v6 or earlier and installing as a
root
orsudo
user, have you tried with thenpm install --unsafe-perm
flag?N/A – npm v 7.19.0
If you are using npm v7, does the user running
npm install
own the directory it is run in?Yes
If you are using the
ignore-scripts
feature ofnpm
, have you tried with thenpm install --ignore-scripts=false
flag?N/A
What is the complete output of running
npm install --verbose sharp
? Have you checked this output for useful error messages?Full Output
What is the output of running
npx envinfo --binaries --system
?The text was updated successfully, but these errors were encountered: