5 ms·
I've gotten annoyed enough to just copy the source from most of my extensions (located at `~/.config/google-chrome/Default/Extensions/`), remove the update stuf
by Zren 8y ago
I've gotten annoyed enough to just copy the source from most of my extensions (located at `~/.config/google-chrome/Default/Extensions/`), remove the update stuff from the `metadata.json` and load them as developer extensions so they never update.
It's easy enough to update them + audit the code when something breaks. The hardest part is downloading the new code (.crx) without installing it, I had to write javascript I paste into the console. StackOverflow can unzip a crx by striping the first 306 bytes.
I forked Stylish v1.5.2 a year ago before I heared of Stylus, but I've no need to to switch since the original extension was pretty good.
https://github.com/Zren/chrome-extension-stylish#fork https://github.com/Zren/chrome-extension-stylish#fork
- e1ven 8y agoI'm glad that workflow works for you. I'm curious though - What about it is better than turning off automatic updates for addons?
- HelenePhisher 8y agoYou can extract the .crx without Javascript using this webservice: http://crxextractor.com/ http://crxextractor.com/ Used it a couple of times in the past, it is a good one.
- Zren 8y agoAll you need to do is remove the first 306 bytes to turn it into a normal zip file. tail -c +307 in.crx > out.zip Credit to this guy in the comments. https://superuser.com/questions/139190/how-to-unpack-a-chrome-theme#comment624001_139198 https://superuser.com/questions/139190/how-to-unpack-a-chrom...
- kav2k 8y agoWould recommend this extension: https://chrome.google.com/webstore/detail/chrome-extension-source-v/jifpbeccnghkjeaalbbjmodiffmgedin https://chrome.google.com/webstore/detail/chrome-extension-s... Allows to easily audit and download the extension right from the Web Store page.