GitHub - code-charity/Manifest-v3: mv2 ⇢ mv3 (manifest.js). Save Browser Extensions! When backwards compatibility breaks, a rainforest of unique relevant (unmaintained) projects vanishes. 🌲🌲🌴🌳

Name		Name	Last commit message	Last commit date
Latest commit History 24 Commits
README.md		README.md

Repository files navigation

Let's not just watch Mf2 extensions expire for xx Million Users...

Can we convert Browser Extensions from Mf2 to Mf3 efficiently / systematically / in bulk?

developer.chrome.com/mv3-overview
developer.chrome.com/mv3-migration
Web Store Archival: wiki.archiveteam.org/Chrome_Web_Store ( Should run again just before ~~2023~~ June 2024? )
📟 developer.chrome.com/blog/Longer extension service worker lifetimes

( MISC: automatically updating all browser extension stores?(through Store APIs & Github actions) )

previously:

About

mv2 ⇢ mv3 (manifest.js). Save Browser Extensions! When backwards compatibility breaks, a rainforest of unique relevant (unmaintained) projects vanishes. 🌲🌲🌴🌳

Custom properties

Report repository

Releases

No releases published

Packages

No packages published