Table of Contents
Ops Fix the damn editor #
I run two IDEs on my system to handle two different development environments.
- VSCode has many nice features I have enjoyed using over the years to work in python with. It is quite glamorous.
- VSCodium is used for working with webframeworks primarily because I had both installed, and was too lazy to be hassled with setting up two different profiles in VSCode.
I have considered ditching VSCodium for sometime now, and go through the burden of setting up a profile and reinstalling everything I use for that profile. Unfortunately, there is never enough time to do this chore.
The drawback of this setup is MicroCrap pulled their usual stunts and VSCode has a completely different marketplace than VSCodium. You used to still use VSCODE extensions in VSCODIUM if you knew a few of the tricks, but it appears now those tricks have now been eleminated. Which means there is very little reason why anyone would want to install VSCodium, because the best extensions will only available on VSCODE. Fortunately, there is another way.
Enter the Hack #
For those who do not fear violating absurdly overreaching and superflous intellectual property laws, there is another way. You can still configure VSCodium to use VSCode’s marketplace instead of it’s own, and it is quite easy to do.
Simply create a json file labeled product.json in your VSCodium configuration directory ~/.config/vscodium, and
place the following lines of code in it.
1{
2 "extensionsGallery": {
3 "serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
4 "cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
5 "itemUrl": "https://marketplace.visualstudio.com/items",
6 "controlUrl": "",
7 "recommendationsUrl": ""
8 }
9}
Close out your editor, and restart VSCodium to load the new configuration.
VIOLA!! You now have VSCode extensions in your VSCodium instance.