Manifest version 2 is deprecated

[FahimFBA]

We are getting an error saying the manifest version 2 is deprecated. Check the picture below.

[TheCedarPrince]

Can confirm I am also getting this but it doesn't prevent the extensions from being used at the moment.

[Cveinnt]

It looks like migrating to V3 manifest is a bit more complicated then I thought - the webpack-extension-reloader package used for this extension is no longer maintained and does not support V3 (more here) which means the service worker registration will fail for v3 manifests.

[ansh]

@Cveinnt We were using v3 before but had to switch to v2 to support Firefox.

Do you have any suggestions on moving back to v3? @mehbubhussain

[asieduernest12]

chrome is the one complaining about version 3 and we can add an extra build step to process the manifest file to work correctly with v3
this also has to account for some of the api calls chrome.tabs.sendMessage and chrome.runtime

[neelkarma]

It looks like migrating to V3 manifest is a bit more complicated then I thought - the webpack-extension-reloader package used for this extension is no longer maintained and does not support V3 (more here) which means the service worker registration will fail for v3 manifests.

Looks like a company maintains a fork of it over at https://github.com/SimplifyJobs/webpack-ext-reloader/ and that there is an issue tracking MV3 support there over at SimplifyJobs/webpack-ext-reloader#28

[asieduernest12]

We can close this, since we are now using the plasmo framework and the chrome build has manifest v3.
i am still learning how to use it well but it looks ok for now. though not version 1 actually so potential issues could arrise.

Firefox build will still be on v2 till they switch the browser to demand v3 by default