microsoft / microsoft/vscode-extension-samples

running wasm-language-server on vscode.dev

Open
#1,230 2 comments 0 reactions 1 assignee View on GitHub

@dbaeumer is already working on this.

Since Oct 23, 2025.

bug
Dominant language
TypeScript
Stars
10.2k
Forks
3.9k
PR merge metrics
No merged PRs in 30d

Description

Extension sample

wasm-language-server

VS Code version

1.105.1

What went wrong?

When trying to run npm run esbuild as per the instructions, it results in

$ npm run esbuild

> wasm-language-server@1.0.0 esbuild
> node ./bin/esbuild.js

✘ [ERROR] Could not resolve "vscode-languageclient/node"

    client/src/extension.ts:7:82:
      7 │ ...geClientOptions, ServerOptions, RequestType } from 'vscode-languageclient/node';
        ╵                                                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The path "./node" is not currently exported by package "vscode-languageclient":

Switching the import line in question from 'vscode-languageclient/node' to

import { LanguageClient, LanguageClientOptions, ServerOptions, RequestType } from 'vscode-languageclient';

gets further, allows npm run esbuild then npm serve then in the command palette install extension from location, things install. Activation seems to begin/log message 'Starting WASM based LSP server'
when a codespace from a git repository is open which seemed like some kind of necessary condition to have a workspace open.

Unfortunately activation fails with:

LSP Client client: couldn't create connection to server.
RAL@https://localhost:5000/client/dist/web/extension.js#vscode-extension:872:15
fromOptions@https://localhost:5000/client/dist/web/extension.js#vscode-extension:1428:50
ReadableStreamMessageReader@https://localhost:5000/client/dist/web/extension.js#vscode-extension:1448:53
startServer2@https://localhost:5000/client/dist/web/extension.js#vscode-extension:20366:24
serverOptions@https://localhost:5000/client/dist/web/extension.js#vscode-extension:20439:49

[Error - 5:43:09 PM] Start failed
RAL@https://localhost:5000/client/dist/web/extension.js#vscode-extension:872:15
fromOptions@https://localhost:5000/client/dist/web/extension.js#vscode-extension:1428:50
ReadableStreamMessageReader@https://localhost:5000/client/dist/web/extension.js#vscode-extension:1448:53
startServer2@https://localhost:5000/client/dist/web/extension.js#vscode-extension:20366:24
serverOptions@https://localhost:5000/client/dist/web/extension.js#vscode-extension:20439:49

Sadly, that change seems to break the local install method (within vscode run on the desktop) with the same error so while it makes it compile, it seems incorrect... Curious is anyone has managed to get that sample working on vscode.dev

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.