New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm package peer-id 0.12.3 incompatible with other 0.12.x #96
Comments
@jacobheun It looks like you have the power to fix this, could you please take a look? |
This looks like it might be an issue with v3 of async caolan/async#1653 (comment) |
It totally was. Thank you! Sorry for the misdiagnosis @ peer-id team |
I think I am going to go ahead and cut a new patch release to roll back to async 2.6. Since we're migrating to |
@jacobheun multistream-select is also using async@3 |
@alanshaw yeah, noticed that last night when I was testing, I will roll the version back there as well. |
* revert(dep): use async 2.6 instead of 3 libp2p/js-peer-id#96 (comment)
Just closing the loop here, both peer-id (12.x) and multistream-select have had their |
I just tried to update the ipfs npm package, and it bumped my version of
peer-id
from0.12.2
to0.12.3
(because many things in the ipfs tree rely on~0.12.x
or^0.12.x
), but then I started getting this error upon building with browserify:Could you please remove version 0.12.3 or replace it with something compatible with all the other packages asking for
~0.12.0
?Update:
Steps to reproduce the error:
package.json
index.js
run
Also available to be cloned here: https://github.com/npfoss/js-ipfs-bug-code
The text was updated successfully, but these errors were encountered: