KubaP
commented
1 week ago Hi! That's cool honestly; I wouldn't have thought there would be enough interest to publish this extension to openvsx, but that's absolutely fine with me. I probably should care a bit more about people using non-microsoft vscode.
I think it'd be good to transfer ownership to me. I have a CI/CD workflow setup that automatically publishes to the Microsoft extension marketplace, so I could easily add a step to publish to the openvsx marketplace too. That way openvsx would always have the latest version automatically.
megatank58
Hi there!
I had published your extension (v1.3.5) to the open-vsx registry 2 years ago under your namespace. The current extension is on v1.5.0. I realize I should have asked this before publishing but are you fine with me publishing or would you like to claim ownership of/take down the extension.
Context
Unfortunately, Microsoft prohibits usages of the Microsoft marketplace by any other products or redistribution of
.vsixfiles from it, in order to use VS Code extensions in non-Microsoft products.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 publishcommand to publish your extension. There's also a doc explaining the whole process with an example GitHub Action workflow.