Official Publising in `Open VSX Registry`

[alek13]

English

English | 中文 (Chinese)

---

Problem

1. There is no official extension available under the same publisher (tangzx).
2. Consequently, it is impossible to fully specify tangzx.emmylua as a dependency in our Luanti API extension.

Short Guide (Full version: Eclipse OpenVSX Wiki):

1. Account Setup

1. Log in to open-vsx.org using your GitHub account.
2. Go to your profile settings to create/link an account at accounts.eclipse.org. Link your GitHub account to it and sign the Open VSX Publisher Agreement in your profile.

2. Namespace (Publisher) Creation

1. In your Open VSX dashboard, navigate to Namespaces.
2. Create a namespace that strictly matches the "publisher" field in your package.json — tangzx.

3. Extension Publishing

1. Package the extension into a .vsix file locally ($ vsce package <options> or $ npx ovsx publish <options>).
2. Click the Publish button in the top menu on open-vsx.org.
3. Click Publish Extension.
4. Drag and drop or browse to select your compiled .vsix file, then confirm the upload.

4. Verify Your Namespace

Create a "Claiming namespace Voxrame" issue.

---

中文版 (Chinese)

English | 中文 (Chinese)

---

问题描述

1. 在相同的发布者（tangzx）名下，目前没有官方发布的扩展。
2. 因此，无法在我们的 Luanti API 扩展中完整且正常地将 tangzx.emmylua 指定为依赖项。

简明教程 (完整版本: Eclipse OpenVSX Wiki):

1. 账户设置

1. 使用您的 GitHub 账号登录 open-vsx.org。
2. 进入个人资料设置页面，创建或绑定 accounts.eclipse.org 账户，并在其个人资料中关联 GitHub 以及签署 Open VSX Publisher Agreement（发布者协议）。

2. 创建 Namespace (发布者)

1. 在 Open VSX 控制面板中前往 Namespaces（命名空间）。
2. 创建一个命名空间，其名称必须与您 package.json 中的 "publisher" 字段严格一致 —— 即 tangzx。

3. 发布扩展

1. 在本地将扩展打包为 .vsix 文件（执行 $ vsce package <options> 或 $ npx ovsx publish <options>）。
2. 点击 open-vsx.org 顶部菜单中的 Publish（发布）按钮。
3. 点击 Publish Extension（发布扩展）。
4. 拖拽或选择您已打包好的 .vsix 文件，并确认上传。

4. 验证您的命名空间

提交一个 "Claiming namespace Voxrame"（认领命名空间）的 Issue。

[CppCXY]

1. I am not tangzx, so I cannot publish under this publisher.
2. the EmmyLua plugin is actually distributed separately for different systems, and the VSIX files used for different systems are different; I think OpenVSX may not support this.
3. I do not want to maintain a platform that I would almost never use.

[alek13]

@CppCXY

1. I am not tangzx, so I cannot publish under this publisher.

Nope. You can :) As you are maintainer of this extension.
Moreover, after namespace tangzx will be created, you can add @tangzx (and others) to it and grant access.

2. the EmmyLua plugin is actually distributed separately for different systems, and the VSIX files used for different systems are different; I think OpenVSX may not support this.

Nope. :) Exactly the same format.

3. I do not want to maintain a platform that I would almost never use.

Open VSX -- alternative for all forks of VS Code (just because Microsoft's license prohibits the use of its marketplace in any third-party builds and forks) .
And there is a huge scope of popular and modern IDEs based on VS Code (forks), that are use Open VSX:

• VSCodium
• Cursor
• Devin (Windsurf)
• Kiro IDE
• Eclipse Theia
• Kodik
• ...

most of them is modern AI-oriernted IDEs, which are increasingly gaining popularity and capturing the market.

[CppCXY]

In fact, VSCode‑based shell IDEs can use extensions downloaded from the official VSCode repository (since VSCode itself provides a download feature for extensions). Although these shell IDEs are generally prohibited from accessing the VSCode extension marketplace, there are many online workarounds to modify the marketplace URL in these IDEs so that they can still use the VSCode store. However, such VSCode‑based IDEs are not becoming increasingly popular nowadays. In reality, Cursor, which was the most popular last year, has been fully acquired this year and its brand will be gradually phased out. Meanwhile, Claude from A\ and Codex from OpenAI are gaining more and more traction among users—to the point that people no longer even need an editor to perform agent‑related tasks.

So actually people are increasingly returning to VSCode, because other AI IDEs don't have that much of an advantage anymore, or else they just stop using VSCode-like editors altogether.

[CppCXY]

Please note that I have received many, many requests to support OpenVSX. The main reasons why I still do not support it are as follows: the current project lacks a LICENSE, and I am not the original author of this project (although I am the actual maintainer), so I do not plan to add a LICENSE. Nor do I intend to fork the project specifically to publish it. Additionally, I want the release process to be fully automated; if it requires me to manually update on certain websites, I will simply refuse. Other reasons are not important.

[alek13]

@CppCXY

I want the release process to be fully automated ... Other reasons are not important.

Agree. And it's possible: https://github.com/eclipse-openvsx/openvsx/wiki/Trusted-Publishing#github-actions