strongloop / loopback

LoopBack makes it easy to build modern applications that require complex integrations.
http://loopback.io
Other
13.22k stars 1.2k forks source link

Installing npm install loopback-component-storage as loopback-datasource-juggler fails #1673

Closed dreamagility closed 9 years ago

dreamagility commented 9 years ago

Hi there,

I've been using loopback successfully (and thanks by the way!) but when I go to use the storage component via "npm install strongloop-storage-component", I get an npm install failture due to the "loopback-datasource-juggler' module not installing correctly.

Error message:

npm ERR! peerinvalid The package loopback-datasource-juggler does not satisfy it s siblings' peerDependencies requirements!

I'm using the most up to date versions of all the dependencies (as far as I know) - as I've run npm update, and the datasource-juggler also failed during this.

package.json dependencies:

"dependencies": { "async": "^1.3.0", "bcrypt-nodejs": "0.0.3", "body-parser": "^1.13.3", "compression": "^1.0.3", "connect-redis": "^2.5.0", "cookie-parser": "^1.3.5", "cors": "^2.5.2", "errorhandler": "^1.1.1", "express-session": "^1.11.3", "fs": "0.0.2", "google-oauth-jwt": "^0.1.7", "http": "0.0.0", "loopback": "^2.14.0", "loopback-boot": "^2.6.5", "loopback-connector-mysql": "^2.1.1", "loopback-datasource-juggler": "^2.19.0", "node-cache": "^3.0.0", "passport": "^0.3.0", "protobuf": "^0.11.0", "request": "^2.61.0", "serve-favicon": "^2.0.1", "socket.io": "^1.3.6", "socket.io-redis": "^0.1.4" }, "optionalDependencies": { "loopback-explorer": "^1.1.0" }, "devDependencies": { "jshint": "^2.5.6" }, "repository": { "type": "", "url": "" },

I get the feeling this may have something to do with version incompatibilities from pre-existing issues such as issues strongloop/loopback#182 and https://github.com/strongloop/strongloop/issues/107.

I'm only asking as I'm unsure how to remedy the issue and would very much like to use the loopback storage component!

dreamagility commented 9 years ago

I managed to fix this by completely removing my node modules folder and re-running npm install. Thanks anyway!