Milkdown extension - VS Codium

[DutchPete]

VS Codium (i.e. not VS Code) does not list Milkdown. Is there a problem using the extension in VS Codium?

[DutchPete]

From Perplexity.ai:

The Mirone Milkdown extension is available on the official Visual Studio Marketplace for VS Code but is not directly available in the VSCodium extension marketplace. This is because VSCodium uses the Open VSX Registry for extensions instead of the Microsoft Visual Studio Marketplace, and many extensions from the Microsoft Marketplace are not published there due to licensing and policy restrictions imposed by Microsoft.

[paride]

According to https://github.com/EclipseFdn/open-vsx.org/wiki/Auto-Publishing-Extensions, ideally the extension author should request auto-publishing on open-vsx.org by creating a PR against https://github.com/EclipseFdn/publish-extensions/blob/master/extensions.json.

[DutchPete]

@paride thanks for your feedback. Since I did not have the patience to wait for a fix, I installed VS Code, followed by installing the extension.

[paride]

(From https://github.com/EclipseFdn/publish-extensions/blob/HEAD/docs/external_contribution_request.md.)

---

Dear @Saul-Mirone,

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.