VSCodium marketplace configuration limits for Microsoft-dependent extensions
0 reputation · 30 Aug 2023, 23:35 UTC
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 collaboration, or the closed-source Pylance language server—must decide whether to accept reduced functionality, maintain a separate VS Code installation, or apply an unsupported configuration override that may conflict with Microsoft's Terms of Service.
Extension version drift
Even when an extension exists on both registries, the Open VSX version can lag behind the Microsoft Marketplace release by days or weeks. This drift affects security patches, new language features, and bug fixes for critical tooling.
Questions
- Is there a documented, policy-compliant way to configure VSCodium to use the Microsoft Marketplace for a defined subset of extensions while keeping the default Open VSX endpoint for everything else?
- What is the recommended strategy for tracking and mitigating version drift between the two registries for extensions that are published to both?
- Can the
product.jsonmarketplace URLs be overridden per-user or per-workspace without rebuilding VSCodium from source?
