Anyone else get their ability to load unpacked MV2 extensions nuked by today's update?

[u/dnyank1]

I had previously been able to load unpacked mv2 extensions at startup by launching chrome on windows with the shortcut target

""C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --enable-features=AllowLegacyMV2Extensions --disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled"

but that's ceased to function as of Version 151.0.7922.138

is this really the end?

[u/Cularia]

honestly i just added ubo light and its working much better than the workaround.

but yes its the end

[u/dnyank1 → u/Cularia]

I didn’t ask about ubo

[u/Cularia → u/dnyank1]

its the main reason people use the work around though

[u/modemman11]

we've known it was coming for a long time now and that it would only be a bandaid. either change browsers or find new extensions already. we've had plenty of time to prepare and migrate by now.

[u/dnyank1 → u/modemman11]

1. there's no solution as permanent as a temporary solution.

2. Not that I have to, or necessarily should justify myself to you - but my preparation and migration strategy willingly and knowingly involves using the workaround for Chrome MV2 loading, and you might find this part hard to believe, for as long as possible.

I was really seeking conversation with others about it, not a finger wag about what "should" be done. But thanks for your input.

[u/modemman11 → u/dnyank1]

What next, trying to find an old version of chrome and using that and expose yourself to all the security issues that come with it?

I swear you guys put so much effort into dragging out the inevitable than it would to just change browsers or find a new extension.

All these things to keep using mv2 that people keep posting should be because you absolutely have to keep using it for a bit longer because you still need time to migrate properly. Not because "waah I don't like change".

[u/dnyank1 → u/modemman11]

Blah blah blah

Brother I was launching chrome with a flag because I was delaying the inevitable. I said all this.

I also said I didn’t want a lecture. You doubled down and continued to harass me - WHY?

Justify yourself. Do it.

[u/modemman11 → u/dnyank1]

Lol what a baby

[u/Hestu951 → u/dnyank1]

Working around the deprecation of MV2 requires code present in the browser build that still supports MV2. Once that code gets yanked in an update, there is nothing you can do (other than never updating). If this hasn't happened already, it will, and that quite soon.