Back when I was still a VSC(odium) user, you needed to perform a small tweak to regain access to the quite useful extensions marketplace (in the sense of, paste the extension ID, see the same results as a M$ VSCode user*): There is a file named product.json which allows you to “regain” access if you populate it with the following values:
(Taken from my old dotfiles, so this may be outdated, not sure. Also, you’ll have to look up the location of this file, it will differ depending on OS. On macOS it goes in ~/Library/ApplicationSupport/VSCodium.)
*If you do not need this 1:1 identical functionality, you may try the Open VSX marketplace. But especially in a class setting, I found this very useful, since all the tutorials/instructions will work without needing adaptation.
To you, @toothpaste_ostrich@feddit.nl, and anyone else planning to do the switch:
Back when I was still a VSC(odium) user, you needed to perform a small tweak to regain access to the quite useful extensions marketplace (in the sense of, paste the extension ID, see the same results as a M$ VSCode user*): There is a file named
product.jsonwhich allows you to “regain” access if you populate it with the following values:{ "extensionsGallery": { "serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery", "itemUrl": "https://marketplace.visualstudio.com/items", "cacheUrl": "https://vscode.blob.core.windows.net/gallery/index", "controlUrl": "" } }(Taken from my old dotfiles, so this may be outdated, not sure. Also, you’ll have to look up the location of this file, it will differ depending on OS. On macOS it goes in
~/Library/Application Support/VSCodium.)*If you do not need this 1:1 identical functionality, you may try the Open VSX marketplace. But especially in a class setting, I found this very useful, since all the tutorials/instructions will work without needing adaptation.
Good to know, thanks for passing this on!