Open VSX registry

[JhonnyJason]

Love stylus and this extension.
Also just switched to VSCodium to limit a bit the potential analysis of my behaviour^^

Unfortunatley I could not find this extension on https://open-vsx.org/ which would be super awesome 😎

For now I use it without this extension - until the pain grows too severe that I would manually download, build and install it.

Thank you and best Regards!

[iChenLei]

Look this comment with previous similar issue, #80 (comment) . Did it help you ?

[JhonnyJason]

Yhea it helps in the way that I had a direct hint where to downaload the .vsix file for installing. So thank you!

However, the beautiful situation would be to have it published on the open marketplace https://open-vsx.org/ as well.
Any reasons why it did not happen then during the thread #80 ?

[tomatopickle]

Any updates on this?, I want to use this in Gitpod

[iChenLei]

@tomatopickle I think your issue is different, stylus not work on vscode-web (gitpod using similiar techology).

[tomatopickle]

Ohkay, Sorry for the trouble

[filiptronicek]

I think your issue is different

Heya @iChenLei, Gitpod can use non-web extensions as well. https://github.dev does not have a backend server, which Gitpod does. This means the reason why this extension does not work there is indeed because of its absence from Open VSX, like @tomatopickle stated.

[filiptronicek]

For Open VSX, me and the team made a document outlying the steps needed in order to publish to both the Microsoft Marketplace and the Open VSX registry. It is available at https://github.com/open-vsx/publish-extensions/blob/master/docs/direct_publish_setup.md.

I would love to help if there are any questions around Open VSX, from what I saw there are many users who would like to use the extension but have to implement workarounds to install it. Feel free to ping me about anything anytime!

[iChenLei]

pin myself

[Santana1053]

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.