Migrate to manifest.json v3.0

[hugolpz]

This actually implies to do a bunch of code migration, with async, etc.

Chrome's migration checklist

Chrome provides a migration checklist which points to more actionable resources :

• Update the manifest : manifest.json, fix syntactic error warnings.
• Update your code
  • Migrate to a service worker
  • Migrate from callback to promise #98 Update API calls
  • Replace blocking web request listeners #100
  • Improve extension security
• Publish on web extension stores #85

V3 from scratch ?

• Crxjs : versatile
• Templates: versatile
• React
• React + vite

Resources

• Firefox > Manifest V3 migration guide
• Chrome > Migrating to Manifest V3
• Extension Manifest Converter

Related

• Explore cross browser format #32 -- require v3 before to move forward.

[hugolpz]

You can now use both when coding and testing locally, thank to YujiSoftware:

"background": {
    "service_worker": "background.js",
    "scripts": ["background.js"]
},

EDIT: remove "scripts": ["background.js"] when packaging your webext for Chrome Web store. Thank to wolfmanstout for this hint.

Source: mozilla/web-ext#2532 (comment)

[kabir-afk]

Mind reviewing the PR if you are free now😅,I mentioned the same under "Additional Info on Cross browser background scripts"😅

[kabir-afk]

When migrating to service worker , we have to convert timers to alarms as well. And under Updating API calls we have to convert callbacks to Promises. I haven't converted timers to alarms yet and I haven't looked upon the latter.

• converted timers to alarms

[hugolpz]

I close this. We consider it done since is works correctly with MV3 approach.

If Chrome / Firefox stores requests changes, it will be to adapt to those stores' requirements, and new issues must be open.