| ▲ | jamisonbryant 2 months ago | |
This right on the heels of the GitLab 17.11 release announcement [0] which mentioned that they added OpenVSX support to their Web IDE. One of the biggest blockers for my team to use the Web IDE/GitLab's equivalent of "Codespaces" was the lack of extensions support. As developers, we're spoiled for widespread (e.g.) vim keybindings support in just about any IDE via extensions. When unable to use it in something like Web IDE, it is very frustrating and makes it less useful as a product. [0]: https://about.gitlab.com/releases/2025/04/17/gitlab-17-11-re... | ||
| ▲ | mdaniel 2 months ago | parent [-] | |
If I didn't hate GitLab's gitlab-org/gitlab issue tracker so much I'd go look to see if them offering OpenVSX registry was on the roadmap, because then an organization could mirror the .vsix into their GitLab instance and not suffer outages (in addition to the supply chain safety aspects) Also, I wonder how hard it would be to teach VSCodium/Theia to pull extensions from OCI because it seems to work great as a distribution mechanism for Homebrew and allows shipping a .vsix from your own GitHub/GitLab account, since both of those offer no-cost OCI image registries scoped to the project | ||