-
-
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
fatal error: 'vips/vips8' file not found #1882
fatal error: 'vips/vips8' file not found #1882
Comments
I'm getting the same issue. |
Also seeing this attempting to install
We've been running on this specific version of Sharp / Node / GCF for awhile now without any issues, it just began today. |
Guys, please review the documentation and use a libvips compatible container: https://github.com/TailorBrands/docker-libvips |
Get the same issue without installing it on docker |
I have same issue, without docker. |
for Ubuntu users: |
There have been no changes to sharp or the prebuilt binaries since 29th July. I've received about 30 emails and notifications about this problem within the last hour so would expect this to relate to a (transitive) dependency that has been published within the last couple of hours. |
Whatever is causing this problem, it looks like it's affecting pretty much every native node module that provides prebuilt binaries mapbox/node-pre-gyp#477 @imkane This issue is not closed, I am actively working on investigating it right now. |
Sorry, my mistake! I misread the referenced issue statuses. Good luck! |
Is there any way to work around this for now? |
So far I've tried installing libvips-dev (#1882 (comment)) and glib2.0-dev (#1148 (comment)). FROM node:10
...
RUN apt-get update && apt-get install -y glib2.0-dev libvips-dev
...
RUN npm --build-from-source install and the result is still:
|
This one did help so far: ...
RUN apt-get update && apt-get install -y libvips-dev --no-install-recommends
... |
Just ran:
and then
Still got the same error. |
Not for us :( |
Strange. |
Out of desparation I tried Yarn and I'm surprised to report that it works for me. I installed on Debian Buster from these instructions and when I ran
Of course, using Yarn is just a temporary workaround, but it might help if you're in a pinch. @lovell Thanks so much for your work on this module! |
Yes it worked on Docker with Node 12.10.0 image with libvips-dev. |
It looks like commit isaacs/minipass@40e1d61 might have collided with mafintosh/end-of-stream#11 and/or commit isaacs/minipass@69888eb might have collided with isaacs/node-tar@42fe53b This will affect most modules that (transitively) depend on Pinning minipass to v2.7.0 should workaround this for now. For those using "resolutions": {
"minipass": "2.7.0"
}, |
Follow up on this issue here: |
This also worked for me. |
#1882 (comment) <-- this worked for me! Thanks so much, @lovell 🙏 |
I have the same problem, it was because my network I couldn't download |
I'm using lerna with npm. For those who are using npm and not yarn. Add minipass as a dependency or dev-dependency depending on where your issues lie.
For me this affects:
|
+ This reverts commit 1b7bafd + Transitive dep minipass is currently sick and failing the build - see lovell/sharp#1882
Adding The sharp installation docs says:
My current sharp installation has no
|
Adding
as @lovell suggested worked for me! |
This works, but the same error when I install |
This also fixed the installation problem for us |
…t found` `minipass` 依赖项导致了该问题,目前通过 `resolutions` 字段、Yarn 包管理器来解决该问题。问题细节参见: - lovell/sharp#1882 - isaacs/minipass#9
Encountering this issue with turtle-cli. Will attempt the suggested solution and report back |
This workaround fixed the issue for us as well. Using |
expo-cli does not work even with minipass added into dependencies. |
添加minipass可以正常编译了 |
This issue is fixed for me with |
it works again for me too, even without adding minipass. thnx for investigating
|
There was a breaking change in v2.8.2 of the upstream If you work at a for-profit organisation that relies on sharp, and I can tell there are a lot of you based on the sheer volume of emails and notifications I've received about this problem over the last 15 hours, please consider donating to the libvips OpenCollective at https://opencollective.com/libvips to say thank you and help with its continued support. |
I've removed the resolution for minipass and can confirm it works. Thank you @lovell |
- Bump travis node version to 12 - Bump minipass to 2.8.5 to fix lovell/sharp#1882 (comment)
I used |
I'm having problems installing sharp in a clean node:12 container.
The issue is quite unfamiliar to me and i havent find the cause yet. Im posting early hoping somebody can point me in the right direction.
The text was updated successfully, but these errors were encountered: