You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Microsoft.VisualStudio.Code.WebResource and Microsoft.VisualStudio.Code.WebExtension should be supported. If such information is indexed then we should reindex existing extensions.
Hey, we experienced similar issues when testing the Vim extension with code-server; here's a few notes:
So, VSCode, for Web extensions, appears to always fetch files directly from the extension gallery CDN (as far as I can tell). This presents two issues: exposing the extra files via the search API and serviing them via the CDN, and also maintaining old versions.
I'm not sure if Open-VSX internally stores old versions - from my tests with querying the service URL, it only appears to return the latest version. Not having past versions can cause issues where the serve has not updated to the newer version, but the client cannot find the old version on the extension gallery.
Reacted by Joe Previte, Brian King and Dean Sheather
I'm planning to work on this within this or next month.
Reacted by Joe Previte, Rush Tehrani, Cano-Muniz, Santiago, Anton Kosyakov, Brian King, Dean Sheather, Olivier Benz, Jan Keromnes, oruharo, Tyler Benster and 5 more
Reacted by Ayase Minori, signed-log and Matt Burman
@danieldietrich did some great work on this, and it all looked good in the staging tests. But for some reason it does not work fully in production yet.
@danieldietrich did some great work on this, and it all looked good in the staging tests. But for some reason it does not work fully in production yet.
Not fully work. Is this mean not all extension works. Is vim working in production mode ?
Hi! When hosting open-vsx in a test environment, including a 'web' instance of vscode, the vim web extension works fine with my changes. However, requesting the web assets in the open-vsx.org production env currently leads to 404 errors. It may be an infrastructure problem, I am still investigating it (without having access to the infrastructure).
Activity
oxy commentedon Feb 24, 2021
Hey, we experienced similar issues when testing the Vim extension with code-server; here's a few notes:
So, VSCode, for Web extensions, appears to always fetch files directly from the extension gallery CDN (as far as I can tell). This presents two issues: exposing the extra files via the search API and serviing them via the CDN, and also maintaining old versions.
I'm not sure if Open-VSX internally stores old versions - from my tests with querying the service URL, it only appears to return the latest version. Not having past versions can cause issues where the serve has not updated to the newer version, but the client cannot find the old version on the extension gallery.
spoenemann commentedon Mar 10, 2021
I'm planning to work on this within this or next month.
gengjiawen commentedon Jun 11, 2021
Is this fixed by #262 ?
spoenemann commentedon Jun 11, 2021
@danieldietrich did some great work on this, and it all looked good in the staging tests. But for some reason it does not work fully in production yet.
gengjiawen commentedon Jun 11, 2021
Not fully work. Is this mean not all extension works. Is vim working in production mode ?
danieldietrich commentedon Jun 11, 2021
Hi! When hosting open-vsx in a test environment, including a 'web' instance of vscode, the vim web extension works fine with my changes. However, requesting the web assets in the open-vsx.org production env currently leads to 404 errors. It may be an infrastructure problem, I am still investigating it (without having access to the infrastructure).
akosyakov commentedon Jun 19, 2021
I just was able to install VIM extension from Open VSX in Gitpod and it runs alone in browser web worker:

@danieldietrich @spoenemann Thank you for all work on it!