violentmonkey
violentmonkey copied to clipboard
violentmonkey
New Chrome version doesn't support it
New Chrome version (133.0.6943.142) doesn't support violentmonkey anymore. Can you make it support new Chrome version?
You can enable ManifestV2 manually: https://stackoverflow.com/questions/79283218
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:
- Go to
chrome://flags/ - Search for
mv2 - Set to Enabled: "Allow legacy extension manifest versions"
- Set to Disabled: the 3 remaining ones, all named "Extension Manifest V2 Deprecation ... Stage"
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.
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:
- Go to
chrome://flags/- Search for
mv2- Set to Enabled: "Allow legacy extension manifest versions"
- Set to Disabled: the 3 remaining ones, all named "Extension Manifest V2 Deprecation ... Stage"
This is a temporary solution that will cut off a lot of users. The flags will be removed soon. It needs to be ported to version 3.
You can enable ManifestV2 manually: https://stackoverflow.com/questions/79283218
@tophf It's not working with new chrome version 134.0.6998.45
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" button element in DevTools and remove the disabled attribute. Then you can install Violentmonkey. Tested in 134.0.6998.89.
The following one-liner can also enable the "Add to Chrome" button:
document.querySelector('button[jsaction^="click"][disabled]').disabled = false;
It sucks that it nuked all of my scripts though
me too. Chrome sucks
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
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.
@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's working.
It works for now, but it's temporary. Are there any plans to update to manifest v3?
It's working.
It works for now, but it's temporary. Are there any plans to update to manifest v3?
Similar issue here: https://github.com/violentmonkey/violentmonkey/issues/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
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
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
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.
You can edit the "Add to Chrome"
buttonelement in DevTools and remove thedisabledattribute. Then you can install Violentmonkey. Tested in134.0.6998.89.The following one-liner can also enable the "Add to Chrome" button:
document.querySelector('button[jsaction^="click"][disabled]').disabled = false;
This worked.
For anyone who isn't tech-savvy:
F12 Go into Console Copy and Paste: document.querySelector('button[jsaction^="click"][disabled]').disabled = false;
If you get a pop-up, just write "allow pasting" and then paste it again.
Then button should be functional :)
Are there any plans to update this extension to Manifest V3?
#https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline
Starting in June, the branch for Chrome 139 will begin, in which support for Manifest V2 extensions will be removed from Chrome. Unlike the previous changes to disable Manifest V2 extensions which gradually rolled out to users, this change will impact all users on Chrome 139 at once. As a result, Chrome 138 is the final version of Chrome to support Manifest V2 extensions (when paired with the ExtensionManifestV2Availability key).
#https://chromiumdash.appspot.com/schedule Chrome 139 goes Stable Release 8/5/2025. At that point, there will be no method at all to enable this extension.
Are there any plans to update this extension to Manifest V3?
#developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline
Starting in June, the branch for Chrome 139 will begin, in which support for Manifest V2 extensions will be removed from Chrome. Unlike the previous changes to disable Manifest V2 extensions which gradually rolled out to users, this change will impact all users on Chrome 139 at once. As a result, Chrome 138 is the final version of Chrome to support Manifest V2 extensions (when paired with the ExtensionManifestV2Availability key).
#chromiumdash.appspot.com/schedule Chrome 139 goes Stable Release 8/5/2025. At that point, there will be no method at all to enable this extension.
use tampermonkey instead
I updated the Development build of Chromium today from 139.0.7225.0 to 139.0.7233.0 and now quite a few of my extensions are disabled with no way of enabling them again... 😕
And yes, I've set the policy and the flags some time ago.
So, this seems to be the end of the road for this wonderful extension (and more).
