Skip to content
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

Chrome problems #2

Open
BubuAnabelas opened this issue Jun 10, 2020 · 0 comments
Open

Chrome problems #2

BubuAnabelas opened this issue Jun 10, 2020 · 0 comments

Comments

@BubuAnabelas
Copy link
Owner

BubuAnabelas commented Jun 10, 2020

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.

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

No branches or pull requests

1 participant