Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

multiaddr dependency missing #140

Closed
vijayee opened this issue Apr 11, 2016 · 8 comments
Closed

multiaddr dependency missing #140

vijayee opened this issue Apr 11, 2016 · 8 comments

Comments

@vijayee
Copy link

vijayee commented Apr 11, 2016

The 'multiaddr' module seems to be missing from the dependency list causing failure when executing 'IPFS()'. Also of note there appears to be a failing peerDependency of karma-webpack on an older version webpack.

@daviddias
Copy link
Member

peerDependency of karma-webpack on an older version webpack.

WebPack uses peerDependencies (unfortuantely) and so it conflicts with a older version that you might have installed globally. Do npm uninstall webpack -g and npm i again on this repo and check if it is all ok

@daviddias
Copy link
Member

Do you still see that issue?

@vijayee
Copy link
Author

vijayee commented Apr 14, 2016

No unfortunately. Webpack was installed globally but after removal and install locally resulted in the same error message as follows.

npm ERR! node v4.4.2
npm ERR! npm  v2.15.0
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package webpack@2.0.7-beta does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer karma-webpack@1.7.0 wants webpack@^1.4.0

the error is not critical everything seems to work anyway. However the missing 'multiaddr' stops you from var node = new IPFS()

@daviddias
Copy link
Member

We've updated the master branch to have multiaddr as a dep.

On the Webpack issue, which npm version are you using?

@dignifiedquire
Copy link
Member

On the Webpack issue, which npm version are you using?

it says in the error message v2.15.0

@daviddias
Copy link
Member

@vijayee you will need npm 3 to work with Webpack. run npm i -g npm

@daviddias
Copy link
Member

@vijayee any update here? All good?

@daviddias
Copy link
Member

As we can't reproduce, I'm closing this one. Let us know if you run into the issue again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants