-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate from manifest version 2 #2
Comments
i think that would be a good idea especially because the more promise-based APIs are really good for code quality, but i would wait for firefox support of manifest v3, last i checked it isn't there yet (not even a roadmap from mozilla) still, it would be possible promisify the extension in manifest v2 with this chrome polyfill from mozilla: https://github.com/mozilla/webextension-polyfill I am just writing my thoughts here because i am interested in the whole manifest thing, also it would be interesting to know if this extension is using any APIs that are being removed with manifest v3 and therefore would require a little more work to migrate (january 2023 is not that far away anymore) |
Hi, we prepare. There are 100 000 extensions though who don't. So we look forward to help part of them in time, here: https://github.com/code-for-charity/manifest-v3 Each predictable, necessary change can also enable us to do tons of (semi-)automatic git pull requests. Saving a lot of Dev-time in sum. This includes even/especially the easiest steps. @code-for-charity/contributors - tagging for once as i believe all of you care about Browser Extensions in 2023 |
Problem i had already do that in some of repo of some extension i used to use ... who where abandoned by their owner |
Hi! @BirdInFire exactly!
|
wow this is huge. i hope it will make developing easier and faster, otherwise it will be nuts... |
When loading the unpacked extension, Chrome 99.0.4844.82 x64 throws an "error" about the manifest version being deprecated. It will be removed in 2023.
More details at https://developer.chrome.com/blog/mv2-transition/
The text was updated successfully, but these errors were encountered: