microsoft / microsoft/vscode-wasm
Installation of "ms-vscode.wasm-wasi-core" is broken in devcontainers
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 456
- Forks
- 40
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 4
Description
Summary:
The extension is installed as disabled
Expected results:
The extension is installed, activated and enabled
Symptoms
This extension is disabled in this workspace because it is defined to run in the Remote Extension Host. Please install the extension in 'Dev Container: sample-dotnet-wasi-vscode' to enable it.
Workaround
Manually install/enable the extension inside the devcontainer.
This is a tedious manual step and a bad user experience in general.
Steps to reproduce:
use devcontainer.json with the following content
{
"name": "sample-dotnet-wasi-vscode",
"image": "mcr.microsoft.com/devcontainers/base:bullseye",
"features": {
"ghcr.io/devcontainers/features/dotnet:1": {
"version" : "8.0.100-preview.6.23330.14",
"installUsingApt": false
}
,"ghcr.io/devcontainers/features/node:1": {}
,"ghcr.io/wxw-matt/devcontainer-features/command_runner:latest": {
"command1": "wget https://github.com/WebAssembly/wasi-sdk/releases/download/wasi-sdk-20/wasi-sdk_20.0_amd64.deb",
"command2": "sudo apt install ./wasi-sdk_20.0_amd64.deb",
"command3": "rm ./wasi-sdk_20.0_amd64.deb"
}
}
,"containerEnv": { "WASI_SDK_PATH": "/opt/wasi-sdk" }
, "customizations": {
"vscode": {
"extensions": [
"ms-vscode.wasm-wasi-core"
]
}
}
,"postCreateCommand": "dotnet workload install wasi-experimental"
,"remoteUser": "vscode"
}
VSCODE version
➜ code --version
1.80.1
74f6148eb9ea00507ec113ec51c489d6ffb4b771
x64
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the supplied devcontainer.json reproduction and the ms-vscode.wasm-wasi-core extension configuration, then inspect how installation and activation are handled for the Remote Extension Host. Done means the extension is installed, enabled, and activated automatically inside the devcontainer without the manual workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode, wasm
- Domain
- developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100