Closed olivier-nerot closed 4 years ago
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review. In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment. Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:
Finally, remember to use https://discuss.ipfs.io if you just need general support.
ipfs@0.46.x
shipped with libp2p@0.27.x
so this would only break if you're trying to use libp2p@0.28.x
compatible modules with libp2p@0.27.x
.
That said, ipfs@0.47.x
has just shipped with libp2p@0.28.x
so you should be good now.
Hello,
From a fresh install, when I do a
npm install ipfs
oryarn add ipfs
, the installed version is 0.46, as waited, but the package.json includes surprisingly old libp2p libraries. For example'libp2p-kad-dht': '^0.18.7'
, even if the latest package.json asks to use"libp2p-kad-dht": "^0.19.5"
. This breaks code, as 0.18.7 still use peerInfo, whereas ipfs send peerid, for example.After having removed node_modules directory, I do
yarn add ipfs
, thenyarn info ipfs
, which returns :