You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a project with dependency to sharp 0.26.1 through another dependency. When I try to install the project it fails with sharp@npm:0.26.1 must be built because it never did before or the last one failed. Checking the build errors the error is fatal error C1083: Cannot open include file: 'vips/intl.h': No such file or directory. Same build works with yarn1 and npm. The possible fixes listed on sharps github issues didnt help.
Installing sharp on yarn1 and then copying the build to node_modules/sharp manually makes everything work also.
Thanks for reporting this one. I have tried to debug this with @Excaa and just side note the .yarn/releases has specific berry build we're using right now, it's the 2.3.3 with patch to the fsevents install (#2078 (comment)). I was not able to use jest without the fix.
I have a project with dependency to sharp 0.26.1 through another dependency. When I try to install the project it fails with
sharp@npm:0.26.1 must be built because it never did before or the last one failed
. Checking the build errors the error isfatal error C1083: Cannot open include file: 'vips/intl.h': No such file or directory
. Same build works with yarn1 and npm. The possible fixes listed on sharps github issues didnt help.Installing sharp on yarn1 and then copying the build to node_modules/sharp manually makes everything work also.
Minimal project to reproduce the issue can be found here: https://drive.google.com/file/d/1sjHMp_xtoH4BCd3_P3k_9DjtgKUI9RZC/view?usp=sharing
Taking the test package out of workspace structure and running 'yarn' (yarn1) or 'npm i' works without a problem.
Environment if relevant (please complete the following information):
If this sounds more like a problem on the sharp side, please let me know and I'll ask there.
The text was updated successfully, but these errors were encountered: