ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #vscodium
Extension Interoperability and Product Identification VSCodium distributes a telemetry-free version of the VS Code source, utilizing the Open VSX Registry as the primary extension gallery. This is achieved by modifying the product.json configuration to redirect gallery endpoints away from the Microsoft Marketplace. A technical challenge arises when extension
Stale extension metadata cache in VScodium's Extensions view The goal is to have the Extensions sidebar always display the most recent version numbers and update notices from the marketplace without manual refresh or restart. Current behavior shows outdated metadata on builds that inherit VS Code caches, and it is unclear whether the cache is shared globally
VSCodium uses community-hosted releases instead of Microsoft's update infrastructure. The Update Service component can surface update availability and verification as silent or generic failures in the user workflow, with behavior that varies by distribution channel and release build. The accessibility surface is inherited from VS Code, including keyboard nav
Goal: Deploy a production VSCodium fleet that installs the exact same extensions used in a developer’s local VS Code workspace without manual intervention. Constraint: Several required extensions are published only to Microsoft’s Visual Studio Marketplace and carry licenses that prohibit redistribution outside Microsoft‑branded builds, so they are absent fro
Marketplace endpoint constraints VSCodium ships with product.json pointing to the Open VSX Registry, and the official documentation does not describe a supported method for switching to the Microsoft Visual Studio Marketplace. Organizations that require extensions relying on Microsoft-proprietary APIs—such as Azure account authentication, Live Share collabor
Scope of VSCodium's telemetry removal VSCodium is documented as a telemetry-free build of VS Code: Microsoft's data collection is disabled at build time, and the extension API is identical, so the same extensions install and run unmodified. Settings sync can also be enabled without Microsoft collecting the associated telemetry. What is less clear is the boun
Extension Gallery Configuration VSCodium is distributed as a telemetry-free binary of VS Code Source. By default, it utilizes the Open VSX Registry for extension discovery and installation rather than the official Microsoft Visual Studio Marketplace. Certain proprietary extensions, such as the C# Dev Kit or Live Share, are licensed specifically for official
Extension Discovery Limitation VSCodium's built-in extension marketplace is configured to use the Open VSX Registry by default, which means extensions published exclusively to Microsoft's Visual Studio Marketplace are not discoverable or installable through the standard extension UI. Primary Constraint The product.json in VSCodium installations sets the exte
The goal is to assess whether extensions published to the Microsoft Visual Studio Marketplace can be used in VSCodium without violating the Marketplace’s Terms of Service or compromising editor stability. By default VSCodium points to the Open VSX Registry, but users may edit product.json to redirect the extension gallery to the Microsoft Marketplace, a chan