-
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
This split comes from the move we did a while back to https://code.visualstudio.com/docs/remote/vscode-server#_architecture. We run a webcontainer process with vscode server, and so all extensions in webcontainer are ran inside node.js processes. The browser extensions i haven't personally been able to install yet, but they are web worker extensions and run in a more restricted sandbox. They're more lightweight than webcontainer ones and often are made to be specifically browser-compatible - whereas webcontainer ones sometimes can be hit and miss depending on whether they use native linux commands etc. which we don't support But yeah the split is confusing because everything is running in your browser tab, we might get rid of the browser panel in the UI if it's not required (will have to investigate). Thanks for reminding us |
Beta Was this translation helpful? Give feedback.
This split comes from the move we did a while back to https://code.visualstudio.com/docs/remote/vscode-server#_architecture. We run a webcontainer process with vscode server, and so all extensions in webcontainer are ran inside node.js processes.
The browser extensions i haven't personally been able to install yet, but they are web worker extensions and run in a more restricted sandbox. They're more lightweight than webcontainer ones and often are made to be specifically browser-compatible - whereas webcontainer ones sometimes can be hit and miss depending on whether they use native linux commands etc. which we don't support
But yeah the split is confusing because everything is running in…