New Chrome version doesn't support it #2284
Comments
|
You can enable ManifestV2 manually: |
|
It sucks that it nuked all of my scripts though |
me too. Chrome sucks |
|
If you apply the settings from the link posted by @tophf before interacting with the notification prompt, and restart Chrome, it won't affect your scripts. In short:
|
|
Yeah, the issue was I clicked a bookmark immediately when starting chrome and it closed the pop-up, which nuked I don't even know what extensions along with their associated settings |
|
so does this mean that Violentmonkey won't support the new version, and we are reliant until Chrome finally removes the legacy v2 manifest option? |
|
In version 131.0.6778.205, this option"Allow legacy extension manifest versions" was removed |
|
|
|
Can confirm quoted comment worked! Screenshot in case anyone needs it.
|
|
This is a temporary solution that will cut off a lot of users. |
@tophf It's not working with new chrome version 134.0.6998.45 |
|
It's working. |
@tophf Can not install the extension. |
|
Ah, I see, it cannot be installed, but it's working if it was previously installed. You can install a released zip as an unpacked extension. |
|
You can edit the "Add to Chrome" The following one-liner can also enable the "Add to Chrome" button: document.querySelector('button[jsaction^="click"][disabled]').disabled = false; |
ya. it's true. I can't install Violentmonkey on Google Chrome (on another laptop at home), So i use tampermonkey instead. But when I'm installed Violentmonkey on Brave Browser from Chrome Web Store without issue. And Brave Browser still committed Supporting legacy (MV2) Extensions. Ref: continue supporting some Manifest V2 extensions |
|
They support them for now, who knows how long they'll support the extensions out of the priority list |
@gera2ld is it possible to provide the crx in github release so that people can directly download crx extension file without using chrome web store? |
It works for now, but it's temporary. Are there any plans to update to manifest v3? |
Similar issue here: #1934 For some reason the maintainer unpinned it and then pinned this issue instead. It seems pretty clear MV3 support isn't coming, and the Chrome workaround is being removed in June 2025. Caution The maintainer should at least give a big red warning in the readme that your scripts will get nuked if you don't enable the temporary workaround. I've said this before but it's gone unnoticed and would be of great service to this community. |
|
In version 137 ，it cannot be installed or work anymore |
It's a Chrome issue, newer versions of Chrome delete and re-download extensions as soon as they are found to be faulty, and you'll download a half-baked extension if you have a bad internet connection |
|
But I tried reinstalling the installation package for crx, but it still showed an image error and caused the installation to fail
But I tried reinstalling the installation package for crx, but it still showed an image error and caused the installation to fail |
do above and delete the extension and try install again |
|
It works for me when i followed the two tips by **DIGiztal: https://digiztal.blogspot.com/2025/04/how-to-install-violentmonkey-extension-to-chrome-browser-with-code-from-github.html and https://digiztal.blogspot.com/2025/04/how-to-enable-back-violentmonkey-extension-in-chrome-web-store.html. |
This worked. For anyone who isn't tech-savvy: F12 If you get a pop-up, just write "allow pasting" and then paste it again. Then button should be functional :) |
New Chrome version (133.0.6943.142) doesn't support violentmonkey anymore. Can you make it support new Chrome version?
The text was updated successfully, but these errors were encountered: