feat: Publish this extension to Open VSX

[mrhyperbit]

Description

Currently VSCodium, Eclipse Theia, Code - OSS by default uses openvsx, for the users of those product including me can use this extension.

Requirements

• Publish the extension on openvsx

Additional Context

More details at :-

• https://github.com/eclipse/openvsx/wiki/Publishing-Extensions
• https://www.eclipse.org/legal/open-vsx-registry-faq/

[mrhyperbit]

Context

Unfortunately, as Microsoft prohibits usages of the Microsoft marketplace by any other products or redistribution of .vsix files from it, in order to use VS Code extensions in non-Microsoft products, we kindly ask that you take ownership of the VS Code extension namespace in Open VSX and publish this extension on Open VSX.

What is Open VSX? Why does it exist?

Open VSX is a vendor neutral alternative to the MS marketplace used by most other derivatives of VS Code like VSCodium, Gitpod, OpenVSCode, Theia-based IDEs, and so on.

You can read on about Open VSX at the Eclipse Foundation's Open VSX FAQ.

How can you publish to Open VSX?

The docs to publish an extension can be found here. This process is straightforward and shouldn't take too long. Essentially, you need an authentication token and to execute the ovsx publish command to publish your extension. There's also a doc explaining the whole process with an example GitHub Action workflow.

[alestiago]

Thanks @mrhyperbit for opening this issue!

For the time being we're actively working on support for just VS Code. I would personally love to get the extension on as many IDEs as possible but there might be a maintenance cost associated to it (we would like to ensure the best support).
We will reconsider publishing the extension outside VS Code Marketplace once version one is released or if there is enough community interest.

For the time being, are you able to download the latest executable here by clicking Download and installing it in your IDE?

[mrhyperbit]

Absolutely, I've got the extension up and running flawlessly.

The maintenance cost is very low since we could have a github actions workflow to effortlessly publish updates on both the Visual Studio Code Marketplace and OpenVSX Marketplace.

More Details :- Publishing Extension To Open VSX