This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
fresh install of IPFS as dep results in older version of async #907
Comments
Here is what an
|
just quickly published a patch version on libp2p. Could you try to do a fresh npm install on js-ipfs latest master? I'm trying figuring out why that error 'today', since we had fixed all the async/setImmediate a while ago. Did you change your npm version? |
I've nailed it down to this issue occurring in libp2p v0.9.1: libp2p/js-libp2p#108 |
Not running tests with browserify keeps biting us. Would love to have this as part of aegir -> ipfs/aegir#102 |
Won't be an issue once 0.25 is released (tomorrow) #910 🎉 thanks for catching it! |
MicrowaveDev
pushed a commit
to galtproject/js-ipfs
that referenced
this issue
May 22, 2020
License: MIT Signed-off-by: Alan Shaw <alan.shaw@protocol.ai>
This was referenced Dec 13, 2021
This was referenced Jan 24, 2022
This was referenced Apr 28, 2023
This was referenced Apr 28, 2023
This was referenced Apr 28, 2023
This was referenced Jan 9, 2024
This was referenced Jan 10, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Fresh install of IPFS as a dependency results in an installed version that resolved async to version 1.5.2.
Symptom: when browserifying the app, the following error occurs:
When starting IPFS from within the node_modules/ipfs dir:
The text was updated successfully, but these errors were encountered: