profile
viewpoint

Ask questionsVSIX-installed extensions all install as "EditorConfig for VS Code"

Describe the bug A clear and concise description of what the bug is.

Please confirm that this problem is VSCodium-specific

  • [X] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

  • [x] I checked the Docs page and my issue is not mentioned there.

To Reproduce Steps to reproduce the behavior:

  1. Install an extension from VSIX, either through the GUI or command-line tool
  2. Restart the software
  3. Go to list of installed extensions; notice that the extension you just installed is not listed, but 'EditorConfig for VS Code' is
  4. Select 'EditorConfig for VS Code'; notice that the description is for the extension you installed.

Expected behavior Once installed, an extension will appear in the list of installed extensions and remain useful after closing and reopening the software.

Desktop (please complete the following information):

  • OS: Ubuntu MATE 20.04
  • Architecture: x64
  • Version: 1.46.1

Additional context If multiple extensions are installed through VSIX, only one will be preserved, presumably because it thinks they are all 'EditorConfig for VS Code' and thus the others are superfluous. This apprears to favor the extension whose folder name in ~/.vscode-oss/extensions sorts first alphabetically; all other extensions will be deleted.

I found this bug after compiling and installing the Firefox Theme, Hg, and Ignore files extensions, which are not available in Open VSX. Upon restarting, only the Firefox Theme extension was still available, and was listed as 'EditorConfig for VS Code'. I checked the ~/.vscode-oss/extensions directory and found the others had been deleted.

I've tried installing from the official VSIX files, downloaded from the Visual Studio Marketplace website, but the same thing happened. The only workaround I've found is to copy the extension folders into the builtin extensions folder, so that they at least can't be deleted automatically.

I have tried the same thing installing from a freshly-built VS Code (that is, Code OSS - Dev) 1.46.1 and it worked as expected, so this seems to be unique to VSCodium.

VSCodium/vscodium

Answer questions notpushkin

I've hacked together a small script that reuploads an extension from VS Marketplace to Open VSC, which can then be installed correctly in Codium. I'm not sure if it's (((ethical))) to do so (and please don't upload proprietary extensions this way, it's probably illegal) but otherwise it's a working solution.

useful!

Related questions

Replace default icon with vscodium one hot 1
Issue with liveshare extension. - vscodium hot 1
Notarization is required on macOS 10.14.5 hot 1
已经安装vscode了 再安装vscodium会冲突吗? hot 1
VSCodium snap package? hot 1
C# extension's debugging does not work 0x89720010 hot 1
Cannot use Remote Development extension pack hot 1
Github User Rank List