Implement MV3 Checklist

[whizzzkid]

This issue tracks implementation of: https://developer.chrome.com/docs/extensions/mv3/mv3-migration/

ETA: 2023-03-30

Tasks

• Migrate manifest_version: 2 -> manifest_version: 3
• Migrate background.page -> background.service_worker
• fix: Handle metrics breakage issue in mv3 #1171
  • Implement a new build step to build service_worker.js instead of background.html
  • Remove instances of window.
  • Migrate instances of localStorage -> browser.storage.
• Migrate web_accessible_resources -> url specific resources.
• Migrate content_security_policy -> content_security_policy.extension_pages
• Migrate browser_action
• Migrate away from eval
• Migrate chrome.contextMenus.create -> chrome.contextMenus.onClicked
• fetch with cors enabled: fix: allow ipfs-companion browser extension to access RPC API kubo#8690
• redirects with Access-Control-Allow-Origin: Missing Access-Control-Allow-Origin Headers on Redirects kubo#9728

[whizzzkid]

We might need to revisit/refactor ignite-metrics, because mv3 removes the background_page context and replaces it with service-wroker context, i.e. reporting metrics from the background would be the same constraint as if running from within a service worker.

Metrics might break on ipfs-companion, because countly sdk needs window context and mv3 replaces background page with a service-worker context, i.e. no more countly:

• Webpack has been incapable so far of producing an asset free of window references.
• counly-sdk-node has a broken package which does not allow node projects to build, but the team’s advice is to move to the web sdk 🤦🏼  Can't resolve 'cluster' in '/projecta/node_modules/countly-sdk-nodejs/lib' Countly/countly-sdk-nodejs#8
• Another alternative could be injecting countly on every page where metrics need tracking (ugh)

[whizzzkid]

Closed as done.