LSP web extension with worker failed

[liweijian]

I wanna to place this extension under the sample folder:

It looks well and it has been deployed to the web server:

sample/moonbit$ ls
dist  language-configuration.json  LICENSE.txt  package.json  README.md  snippets  syntaxes

$ ls dist/
client.js  client.web.js  server.js  server.web.js

However, when I tried to run on web page, there's an error:

"Uncaught NetworkError: Failed to execute 'importScripts' on 'WorkerGlobalScope': The script at 'https://moonbit/dist/server.web.js' failed to load."

For the extension itself, the syntax highlight works, the snippets works. However, auto-complete not work(It depends on the server.web.js), just wondering if anything I'd missed?

And it's weird that the client.web.js loaded succeed:

[liweijian]

The source code which load the server.web.js:

export function activate(context: ExtensionContext) {
  const clientOptions: LanguageClientOptions = {
    documentSelector: [{ language: 'moonbit' }],
  }
  // Create a worker. The worker main file implements the language server.
  const serverMain = Uri.joinPath(context.extensionUri, 'dist/server.web.js')

  const worker = new Worker(serverMain.toString(true))

  // create the language server client to communicate with the server running in the worker
  const client = new LanguageClient('moonbit', 'Moonbit', clientOptions, worker)

  const disposable = client.start()
  context.subscriptions.push(disposable)
}

This extension works pretty well on VS Code client, not sure if we need to change it to work in web ?

[liweijian]

I did try to add the script from index.html:

<script src="./moonbit/dist/server.web.js"></script>

But the extension's auto-complete still not work:

[liweijian]

I tried to install it from Open VSX, and got the same error:

[liweijian]

And it works in github.dev(see the auto-complete from LSP server)

type u struct {
  x:float
  y:int
}

func init {
    let h = {x:3.1, y:2}
    h.   
}

[lemanschik]

out of scope for this package this is not a VSCODE Implementation it is the packaging process and the dev dependencies to do your own how ever i could extract out of your screen shoots that you got type errors in your code i saw stuff like mixing of importScript:/// so you did maybe write that wrong some where and maybe 100 other failures you need to get eslint up and running first then typescript then proceed.