You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue has been marked as WontFix so it's most likely not going to be fixed anytime soon. The major problem with this issue is that js-ipfs now uses async functions to access the internal methods.
Currently, ipfs-companion uses ipfs@40.0.0 for accessing the IPFS API and its internal methods. They have an open issue for keeping track the migration which could be very useful as a work-around to Chrome's problems.
In the near future, if the user has ipfs-companion installed and window.ipfs enabled, it should be easier to interface with the local node.
The text was updated successfully, but these errors were encountered:
Currently Google Chrome (along with Brave Browser) has one major problem:
This issue has been marked as WontFix so it's most likely not going to be fixed anytime soon. The major problem with this issue is that js-ipfs now uses async functions to access the internal methods.
Currently, ipfs-companion uses ipfs@40.0.0 for accessing the IPFS API and its internal methods. They have an open issue for keeping track the migration which could be very useful as a work-around to Chrome's problems.
In the near future, if the user has ipfs-companion installed and window.ipfs enabled, it should be easier to interface with the local node.
The text was updated successfully, but these errors were encountered: