Feature Request: Publish to Open VSX

[kmf]

Would be possible to also Publish this extension on https://open-vsx.org

---

Four Easy Steps to Publish Extensions

We would love to see extension developers publish to our registry in addition to Microsoft’s. To encourage publishing, we developed a CLI that makes publishing very easy. The four basic steps to publish extensions are:

1. Register on open-vsx.org through GitHub OAuth.
2. Create an access token and copy it.
3. Run npx ovsx create-namespace <publisher> --pat <token> with the publisher name specified in the extension’s package.json.
4. Run npx ovsx publish --pat <token> in the directory of the extension you want to publish.

---

Related Link: https://www.eclipse.org/community/eclipse_newsletter/2020/march/1.php

[marcparadise]

@tas50 thoughts?

[tas50]

That's certainly something we can explore as we look to automating our artifact publishing.

[trinitronx]

I second this request 😄

Thanks to all at Chef for this excellent extension! I've been using it on macOS development machines for a while now for cookbook development and have been loving it.

I'm sure there are others who would love to use this extension but currently can't find it due to the split between OpenVSX / VisualStudio Marketplace repos for OSS builds of VSCode.

In the past few years, many OSS Linux packagers of VSCode, VSCodium, (a.k.a. Code OSS) have moved to using OpenVSX extension Registry and had to disable Microsoft's Extensions Marketplace by default due to Microsoft's licensing restrictions.

So, in order for most Linux developers using stock OSS-packaged versions of VSCode to find extensions such as this one, it's important to also publish to OpenVSX.

Below is some more info from OpenVSX's extension publishing letter template:

OpenVSX Info / Request Template

Dear extension author, Please publish this extension to the Open VSX marketplace.

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.