Skip to main content
Check

MV3

We have updated our extension to manifest versions 3 and deployed on DEV environment.

Chrome is going to stop support for mv2 as per there timeline

I request you all to import your configuration in dev version once and try out if it works seamlessly. As the same version is going to be deployed on beta and stable version soon. if you find any issues with MV3 versions, do create a issue on Github and also add a tag of MV3.

Below are places where we have made changes which are related to MV3. If you find if you have used any of this, you need to test your configuration for same, we have created a separate thread for MV3 on our Discord channel as well. You can ping here directly also

Changes

Important

with MV2 version we were storing all configuration on localStorage . With MV3 they deprecated localStorage and provided similar option which is chrome.storage.local. Because of this change we all must export our configuration from MV2 and import back in extension with MV3 version.

Even though MV3 do not support local storage it do not remove any data from local storage, its stored safe you can follow below steps to recover your configuration in case if you have not saved previously.

Steps

  • go to chrome://extension
  • enable developer mode from top right navbar
  • Click on service worker link within extension card
  • Devtools window opens
  • navigate to Application tab
  • left side sidebar you can navigate Storage -> Local Storage (expand)
  • Click on chrome-extension://<extension-id>
  • You will see
    • configs
    • settings
  • double click value field of both and copy its content and paste it in plain text file
  • save it as [file name] with .json extension
  • you can import this configuration file back into MV3 extension under Bulk import Configuration
mv3
Share on: