Extensions specified in devcontainer.json
file do not install in the correct extension host
#41636
Replies: 4 comments
-
Hey @thegecko sorry you're not having the experience you expect. I'll file a ticket to discuss this further. In the meantime, if you're able to, it might be worth trying to override the installation location in the settings.json file--that could be a potential work around (although I haven't tried it myself). |
Beta Was this translation helpful? Give feedback.
-
Hi @thomas-sickert,
Do you see any other workaround or do I have to wait until the issue is fixed? |
Beta Was this translation helpful? Give feedback.
-
I can also confirm this work around doesn't work. The closest I've got is to use an @thomas-sickert is there any progress on fixing this or a way I can escalate it? |
Beta Was this translation helpful? Give feedback.
-
This is still an issue and VS Code extensions marked as Any update @thomas-sickert ? |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
As outlined over at:
microsoft/vscode#154563
VS Code web extensions specified in a
devcontainer.json
file on codespaces do not install in the correct extension host. From that issue:Steps to Reproduce:
devcontainer.json
file with this extension (e.g. this one)codespace
extensionsExpected behaviour - the multi-host extension should install as a web extension into
browser
extensions.When installing this extension manually, it behaves correctly:
Beta Was this translation helpful? Give feedback.
All reactions