Provide a VS Code web extension entrypoint about oso HOT 4 OPEN

I'm currently trying this out with a custom language server I'm building with a similar setup and think I'm well underway to figuring it out. Will report back today or tomorrow!

from oso.

So I have a proof-of-concept working in my own extension's repo. I'm by no means an esbuild/bundling/extension expert, so I would love to hear any good suggestions/improvements on that front. It works for both the node and browser entrypoint. Some caveats, though:

• the Worker of each client (webworker) doesn't seem to be cleaned up properly if workspace folders change and clients are stopped and restarted in the browser. This can result in duplication of errors. I had to change the path handling to use VS Code's internal Uri type. This gets rid of the dependencies on the path:node and friends, but might be the culprit. Or the worker should be cached somewhere and properly .terminate()d on client stop.
• the WASM is encoded inline in both the JS output files for the servers because I don't know how to bundle it as a single static file properly. For small language servers I think this shouldn't be much of a problem, but it's not quite as elegant as having the plain WASM file in your ./out tree.

Any constructive suggestions are highly appreciated :)
https://gitlab.com/ratio-case-os/rust/esl-compiler/-/tree/main/vsx

from oso.