That's not as trivial because extension that uses node also use the fact that this is the same node instance that runs vscode itself and use vscode API to do "t

That's not as trivial because extension that uses node also use the fact that this is the same node instance that runs vscode itself and use vscode API to do "things". Other things it does is accessing the file system or network which may anyway not work even in a WebContainer. It is pretty easy to port an extension to be able to run as a web extension as well. This is documented there: https://code.visualstudio.com/api/extension-guides/web-extensions https://code.visualstudio.com/api/extension-guides/web-exten... I've done that for my extension. My extension uses a language server through the Language Server Protocol (LSP). In order to make it work as a web extension, I had to compile the language server (written in Rust) to webassembly, and also hack a way to query "import" files via vscode api instead of file system access.