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
{{ message }}
This repository was archived by the owner on Feb 9, 2021. It is now read-only.
VS Code supports remote development. In such cases, the filesystem is not local— it's instead in, say, a remote server accessed through SSH or a container.
There are therefore two kinds of extensions: UI (which run on your laptop) and workspace (which run on the remote host). This extension seems to be miss-labeled as a workspace extension, so in situations where one might be able to enable/install UI extensions (in the local machine) but not change the extensions in the remote host, it can't be used.
This happened to me. I forced this extension to be labeled as a UI extension following the instructions here and it's working normally thus far. Bringing this up since others in the same situation might not know this is why the extension is not available/disabled. This labeling should be fixed (:
VS Code supports remote development. In such cases, the filesystem is not local— it's instead in, say, a remote server accessed through SSH or a container.
There are therefore two kinds of extensions: UI (which run on your laptop) and workspace (which run on the remote host). This extension seems to be miss-labeled as a workspace extension, so in situations where one might be able to enable/install UI extensions (in the local machine) but not change the extensions in the remote host, it can't be used.
This happened to me. I forced this extension to be labeled as a UI extension following the instructions here and it's working normally thus far. Bringing this up since others in the same situation might not know this is why the extension is not available/disabled. This labeling should be fixed (: