You can supposedly make Google #Chrome support #ManifestV2 for a while longer with this registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome]
"ExtensionManifestV2Availability"=dword:00000002
Use that extra time wisely and migrate away from Chrome.
I have already migrated to Firefox for the most part, myself.
But there’s a wrinkle.
In Chrome, once you tell it to load a custom extension, it remembers it and loads it in future sessions. Firefox forgets that extension every time you close the browser. I have several custom extensions (), so I really dislike this.
I am now using Firefox Developer Edition, because it does remember those extensions.
The process of updating them is still more cumbersome than in Chrome, but I’ll take it.
Now I just have to figure out if I can have Developer Edition with different user profiles, loading different custom extensions. And then I have to port my two remaining extensions to Firefox. Which might be a problem, because one of those two is a browser download manager, and the other one intercepts certain downloads and tells the download manager to rename them in a specific pattern.
If you’ve done extension development, you probably already see several problems with this. Sigh.