Manifest v3 compatibility
See original GitHub issueWith the beginning of the next year, 2023, Google will only accept Chrome extensions following the Manifest v3.
Arweave-js
is used by most of the browser crypto wallets and I wonder if there are plans to make it somehow compliant with this new policy.
As far as I know, it should mostly consist of replacing the axios
HTTP client with some other that uses the native fetch
mechanism as XMLHttpRequest
won’t be available.
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:16 (12 by maintainers)
Top Results From Across the Web
Manifest V3 migration guide | Firefox Extension Workshop
Firefox has extended its support for background scripts by enabling non-persistent background pages for Manifest V2 and V3. Using non-persistent ...
Read more >Manifest v3 in Firefox: Recap & Next Steps - The Mozilla Blog
Manifest V3 is the next iteration of WebExtensions, and offers the opportunity to introduce improvements that would otherwise not be possible ...
Read more >Chrome Extensions: Manifest V3 migration checklist
The adoption of service workers in Manifest V3 isn't compatible with methods like chrome.runtime.getBackgroundPage () , chrome.extension.
Read more >January's Firefox release will support Manifest V3 extensions
Mozilla plans to launch support for Manifest V3 extensions in Firefox 109, which it aims to release on January 17, 2023.
Read more >Overview and timelines for migrating to Manifest V3
Manifest V2 extensions will continue to be supported through Enterprise policies at least until Chromium Manifest V2 support timeline (which is ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Update. The actual issue is that arweave-js makes extensive and advanced use of Axios library, which is based on XmlHttpRequest. Manifest V3 only supports the newer Fetch API.
There are a couple of 3rd party Axios adapters that allow you to use Fetch API, however none of these appear to be compatible with arweave-js.
Yes, as it is also required for ArConnect