Web VS Code extensions cannot activate `ms-vscode.wasm-wasi-core`
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- vscode, wasm
- Domain
- devtools
Research direction
Reproduce the failure with the lsp-web-extension-sample, its package.json browser entrypoint, and the default "Run Web Extension" launch option. Trace why the ms-vscode.wasm-wasi-core dependency is reported as not loaded in a web-only extension, then verify that the sample activates successfully without the reload error in the tested web environments.
Written by the indexing model from the issue text.
Description
When writing a web-only VS Code extension, i.e. with a package.json that only defines a "browser" entrypoint, the extension will not activate when depending on ms-vscode.wasm-wasi-core:
"extensionDependencies": [
"ms-vscode.wasm-wasi-core"
]
Minimal working example:
- Install the WASI based WebAssembly Execution Engine from the Marketplace.
- Download the official lsp-web-extension-sample example.
- Add
ms-vscode.wasm-wasi-coreas an extension dependency and run. - The extension will not activate and will display the error:
Reloading the window does not fix the issue.Cannot activate the 'lsp-web-extension-sample' extension because it depends on the 'WASI based WebAssembly Execution Engine' extension, which is not loaded. Would you like to reload the window to load the extension?
Tested on Mac (with the default "Run Web Extension" launch option; VS Code 1.94.0, on Sonoma 14.6.1), and also within a self-hosted web environment.
- Dominant language
- TypeScript
- Stars
- 456
- Forks
- 40
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 3
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from microsoft/vscode-wasm
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/vscode-wasm#249 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
microsoft/vscode-wasm#244 · 2 reactions ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/vscode-wasm#240 ·
-
feature-request
Difficulty 5/5 Over a week Newbie friendliness 28/100
microsoft/vscode-wasm#235 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 25/100
microsoft/vscode-wasm#217 · 3 comments · 2 reactions ·
All issues in microsoft/vscode-wasm
Similar issues
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
opensearch-project/security-dashboards-plugin#2545 ·
Maintainers usually reply within 1 day
-
Add: Dream TR SDOpencheck:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
doctor integrity sample scans soft-deleted pages on Postgres (batch path has no deleted_at filter)Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
SocialGouv/egapro#4672 · 1 comment ·
Maintainers usually reply within 2 days
-
area:agents area:tui bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
anthropics/claude-code#98358 ·
Maintainers usually reply within 1 day