vscode-vsce VS openvsx

Lastly we will package and publish our extension using the Visual Studio Code Extension Manager and a GitHub Action called HaaLeo/publish-vscode-extension. The advantage of having the packaging and publishing step separated is that we can attach the compiled .vsix file as an artifact to the workflow and offer it as download. Make sure to generate a token (named in the workflow as VSC_MKTP_PAT and OPEN_VSX_TOKEN) to allow GitHub to publish your extension.

I'm using VSCE - VSCode Extension Manager package to build and deploy my project to the Marketplace.

There is a CLI tool called vsce for packaging and publishing extensions. It's easy to use. This will create a vsix package that can be installed as an extension.

The following are some of the most common extension types on the Visual Studio Code Marketplace and Open VSX Registry, an open-source, community-driven extension registry for Visual Studio Code (VS Code) extensions.

Eclipse runs the Open VSX registry that VS Codium uses. Eclipse also has a fork of VS Code called Theia.

https://open-vsx.org/

https://theia-ide.org/

The extension is not available on https://open-vsx.org/ ? (The market place for VSCodium)

See also: https://open-vsx.org

Would you consider supporting the open vsx repo in your release workflow for those of us on VSCodium?

I didn't know about https://open-vsx.org/. Very nice! But besides those languages, they are also missing things like the remote ssh extension, which is a big deal breaker for me (and I assume many others regardless of language).

Any chance you could publish it to Open VSX as well, for the people not using the Microsoft version?

no there's lots of extensions available on vscodium, just not the same ones (https://open-vsx.org)

If we do not generate enough interest, we’ll be forced to decommission https://open-vsx.org/ by the end of May, 2023