Enable vetur to work with VS Code on the Web

👋 I’m Isidor, a PM from the VS Code team, and we recently announced VS Code for the Web at https://vscode.dev/, which provides a free, zero-install Microsoft Visual Studio Code experience running entirely in your browser. You can learn more here.

We’d like to ensure vetur can run in the web, and we have a guide for enabling extensions for the web here. As a couple of highlights:

• In VS Code for the Web, both the UI and extension host run inside the browser.
• A web extension is structured like a regular extension, but with a different main file: it’s defined by the browser property
• Access to workspace files needs to go through the VS Code file system API accessible at vscode.workspace.fs
• There are currently three ways to test a web extension

I checked your extension and I see there are quite some node dependencies, so this transition to web might not be trivial. However it would be cool if you could at least contribute grammars for web, and using when clauses disable all other contributions which can not work on the web.

We are also open to helping here. Let us know what you think. Thanks!

@aeschli @octref

[jrieken]

How does the typescript extension solve this problem to support the Web IDE?

This is being worked on. Today, the TypeScript web extension is more or less single file, e.g it doesn’t support cross file features like find references. You correctly pointed out that tsserver is all sync and unfortunately that won’t change. The current plan is to add logic to tsserver to add a virtual, synchronous file system which is updated and initialized by async messages. This is the corresponding issue: https://github.com/microsoft/TypeScript/issues/47600.

[jrieken]

of language server will cause performance issues, it seems not proven in tsserver yet and I have to try.

I do something similar with vscode-anycode and it seems to work. What I do is this: build a glob pattern with all types of files that I support and search for them. I later open them one by one to digest them. There is some tricks and a tad of remote hub knowledge to not get blocked. We are thinking about better API for this but meanwhile that works