search

simonihmig / responsive-image

The multi-framework JavaScript library for responsive images.
https://responsive-image.dev
MIT License
116 stars 17 forks source link

Incompatible library version: libvips-cpp.dylib ... #48

Closed voltidev closed 5 years ago

voltidev commented 5 years ago

Here is an exception I get when I run $ ember s:

Referenced from: ../node_modules/ember-responsive-image/node_modules/sharp/vendor/lib/libvips-cpp.42.dylib
Reason: Incompatible library version: libvips-cpp.dylib requires version 52.0.0 or later, but libvips.42.dylib provides version 51.0.0
OS: macOS 10.14.2
Node: 10.15.0
NPM: 6.4.1
Ember-cli: 3.7.1
voltidev commented 5 years ago

After I installed "sharp": "^0.21.3", I'm getting another exception:

Build Error (Funnel)

ENOENT: no such file or directory, scandir '/var/folders/y7/v91qm2_90tq9d21sxnjd9ndm0000gn/T/broccoli-558563OiaRy1NW8GZ/out-227-broccoli_merge_trees/assets/images/generate/'
Build Error (Funnel)

ENOENT: no such file or directory, scandir '/var/folders/y7/v91qm2_90tq9d21sxnjd9ndm0000gn/T/broccoli-558563OiaRy1NW8GZ/out-227-broccoli_merge_trees/assets/images/generate/'

Just in case, here are my dependencies:

{
    "@ember/optional-features": "^0.6.3",
    "broccoli-asset-rev": "^2.7.0",
    "ember-cli": "^3.7.1",
    "ember-cli-app-version": "^3.2.0",
    "ember-cli-babel": "^7.1.2",
    "ember-cli-dependency-checker": "^3.0.0",
    "ember-cli-eslint": "^4.2.3",
    "ember-cli-fastboot": "^2.0.0",
    "ember-cli-htmlbars": "^3.0.0",
    "ember-cli-htmlbars-inline-precompile": "^1.0.3",
    "ember-cli-inject-live-reload": "^1.8.2",
    "ember-cli-sass": "^8.0.1",
    "ember-cli-sri": "^2.1.1",
    "ember-cli-stylelint": "^2.2.0",
    "ember-cli-template-lint": "^1.0.0-beta.1",
    "ember-cli-uglify": "^2.1.0",
    "ember-composable-helpers": "^2.1.0",
    "ember-export-application-global": "^2.0.0",
    "ember-keyboard": "^4.0.0",
    "ember-link-action": "^0.1.3",
    "ember-load-initializers": "^1.1.0",
    "ember-maybe-import-regenerator": "^0.1.6",
    "ember-qunit": "^3.4.1",
    "ember-resolver": "^5.0.1",
    "ember-source": "~3.7.0",
    "ember-svg-jar": "^1.2.2",
    "ember-truth-helpers": "^2.1.0",
    "ember-welcome-page": "^3.2.0",
    "ember-wormhole": "^0.5.5",
    "eslint-config-airbnb-base": "^13.1.0",
    "eslint-plugin-ember": "^5.2.0",
    "eslint-plugin-import": "^2.14.0",
    "loader.js": "^4.7.0",
    "prember": "^1.0.2",
    "qunit-dom": "^0.8.0",
    "sass": "^1.15.3",
    "stylelint-config-recommended-scss": "^3.2.0",
    "stylelint-config-standard": "^18.2.0",
    "stylelint-scss": "^3.4.4",
    "susy": "^3.0.5",
    "tiny-slider": "^2.9.1",
    "ember-responsive-image": "^1.0.0-rc.6",
    "sharp": "^0.21.3"
}
simonihmig commented 5 years ago

Hm, not sure. Did that happen right after installing this addon, or did you use it already before?

Have you tried yarn upgrade (assuming you use yarn), or clearing node_modules and doing a fresh install (without lockfile)? Or anything else that uses sharp? (yarn why sharp)

simonihmig commented 5 years ago

Closing this due to inactivity. @ivanvotti feel free to reopen should this problem persist, with the feedback requested above.

nickschot commented 5 years ago

I also happened to run into the issue from the OP. For me it seemingly was caused by multiple (older) sharp versions being present because I'm also using ember-cli-image-transformer which depends on the older 0.20.8. Using a yarn resolution field fixed it for me.

I have not run into the issue from the second post.

toovy commented 4 years ago

I'm also running into this issue. In my case this issue arises as I use ember-lazy-responsive-image that has the dependency ember-responsive-image. Both depend on sharp, but on different versions, in my case 

ember-lazy-responsive-image@0.1.0
  - sharp@0.19.1
  - ember-responsive-image@1.0.0-rc.6
    - sharp@0.21.3

After using https://www.npmjs.com/package/npm-force-resolutions to force the dependency to be sharp@0.21.3 it worked. This could issue could probably prevented by maintaining the same sharp version in both projects. Still, when using other ember addons that depent on sharp in the same project this issue might arise again.