Support VS Code / VSCodium

[svenefftinge]

In order to allow VS Code/ VSCodium to connect to openvsx, we need to support the proprietary protocol from MS Marketplace, which needs to be revers engineered.
I think an extra endpoint that understands that protocol and adapts it to openvsx would make sense.

[dsseng]

What's about a CLI? e.g. user'll be able to run openvsx install author.ext with optional path to code executable. CLI will perform these steps: fetch extension from openvsx to temp directory, run code --install-extension <path> and delete the temp file.

[spoenemann]

There is already a CLI that could be extended with such a feature:
https://github.com/eclipse/openvsx/tree/master/cli

But that would be a very different user experience than the Extensions view of VS Code.

[spoenemann]

Parts of the VS Code protocol can be understood from the TypeScript source:

https://github.com/microsoft/vscode/blob/db48c19e86263c9a860e3e2fc3049e98f78c3fc5/src/vs/platform/extensionManagement/common/extensionGalleryService.ts#L488

[spoenemann]

Add this to your product.json to use Open VSX in VS Code:

"extensionsGallery": {
	"serviceUrl": "https://open-vsx.org/vscode/gallery",
	"itemUrl": "https://open-vsx.org/vscode/item"
}

[plmrry]

"extensionsGallery": {
	"serviceUrl": "https://open-vsx.org/vscode/gallery",
	"itemUrl": "https://open-vsx.org/vscode/item"
}

Hi @spoenemann, dumb question: How do I edit product.json? Where does that file live?

[spoenemann]

It's in the root of the vscode repository:
https://github.com/microsoft/vscode/blob/main/product.json

It should be somewhere in your local VS Code installation as well. Where exactly depends on your OS.