microsoft / microsoft/vscode-wasm

Web VS Code extensions cannot activate `ms-vscode.wasm-wasi-core`

Open
#210 11 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
456
Forks
40
Avg merge
3d 2h
Merged PRs (30d)
4

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-core as an extension dependency and run.
  • The extension will not activate and will display the error:
    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?
    
    Reloading the window does not fix the issue.

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
vscode, wasm
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.