Publish the vscode-extension on OpenVSX

[ieris19]

Motivation

I use VSCodium instead of VSCode, and as such, I rely upon openVSX instead of VSCode's Marketplace.

I love this tool and this extension but I need to both compile the vsix myself and check for updates

Solution

Publishing the extension on OpenVSX would be greatly appreciated, and improve the accessibility to those of us looking to stick with OSS as much as possible.

More information can be found on the publishing instructions and an automated GH Actions workflow can be found on the auto-publishing instructions

Alternative options

Since the license is open, technically I can just submit it for autopublishing as described here. But I thought it would be courteous to propose first before taking any actions.

Additional documents

The full wiki can be found here https://github.com/EclipseFdn/open-vsx.org/wiki/Auto-Publishing-Extensions

Additional context

Many of VSCode forks also rely on OpenVSX (notably Theia and all the AI powered ones) so this extension would benefit anyone in the VSCode ecosystem that does not rely upon Microsoft's builds.

The only concern I have would be the Eclipse legal formalities.

[onlyati]

Hello @ieris19,

thank your for reaching me!

I see no issue to publish the extension, I'm just happy if my project can reach more people. But I'm a bit of lack of time to manage it.

Hereby I'm giving my approval to setup the auto-publishing for this extension as you described in the alternative options. If I understand the description well, by this action, I have no further action to do (neither later with new releases) because it is an automated workflow to pull the new versions by openvsx?

[ieris19]

Yeah, as I understand it too, it just publishes whatever is on the VSCode Marketplace to the OpenVSX marketplace. It runs every night and updates OpenVSX if an update has occurred on VSCode Marketplace, so at worst, updates will be a bit delayed over there.

And since the license (and now this message) give explicit permission for redistribution, I'm able to take the steps to set this up myself, so no further action is needed

Thanks for the swift reply! I'll set it up and return here once it's fully posted on OpenVSX to close the issue

[onlyati]

I see you have open the PR, thanks!

I also have seen that you brought up a problem to separately download the binaries. I'm not sure, but it may helps: onlyati/quadlet-lsp-vscode-extension@b3a3bcc#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R109

I've added the download script to happen automatically via vsce package/publish commands. I hope in their CI environment, they have sh, wget, unzip and tar and it can run fine. In case of any issue, we'll cook out something I'm sure.

[ieris19]

From their Github action runs-on: ubuntu-latest so it should be covered. I am pretty sure these are all preinstalled on ubuntu, but the script requires bash (I was the one who added the loop, which currently relies on bash-only features). Either way it should be fine.

I know they also have the option to run extra commands for extensions that might need it, but this should probably completely avoid that need.

Thanks for the support! I think the only other concern I have (and have not really mentioned this before) is that I'm getting a warning that .vscodeignore and package.json attribute files are incompatible, but I am far too inexperienced with extensions to know better. Locally I tend to delete .vscodeignore and rely on the files array but I am not sure how their CI or you deal with this.

[onlyati]

About that file vs .vscodeignore, I'm not sure what would be the best. I'm not that experienced with VS Code and its extensions too (I'm rather a neovim guy). But we will see once it is running if something missing :-)

Anyway, I changed the bash dependency to sh too, to make it be able to run on more distros.