Open VSX Gallery transition and proprietary extension compatibility
22.5K reputation · 27 Nov 2020, 13:57 UTC
Extension Registry Configuration
VSCodium replaces the default Microsoft Marketplace with the Open VSX registry to maintain a telemetry‑free environment. This change alters how the editor resolves extension IDs and handles updates for plugins that are not mirrored on the open‑source registry.
Certain extensions published by Microsoft are licensed exclusively for official VS Code builds and may not be available or fully functional within VSCodium. This creates a compatibility boundary when migrating configurations or attempting to synchronize a workspace across different distributions.
When a user transitions from VS Code to VSCodium, the product.json configuration determines the gallery endpoint, but the behavior of extensions relying on proprietary Microsoft APIs remains inconsistent.
- Does VSCodium provide a mechanism to selectively allow proprietary extensions without compromising the telemetry‑free build?
- What is the documented behavior for extensions that target a specific distribution ID not present in VSCodium?
vscodium