Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web extension #6

Open
ratmice opened this issue Apr 22, 2022 · 0 comments
Open

Web extension #6

ratmice opened this issue Apr 22, 2022 · 0 comments

Comments

@ratmice
Copy link
Owner

ratmice commented Apr 22, 2022

There are a few impediments to making this work as a web-extension, vscode-web is probably worth looking at too

first need to compile to wasm, tower-lsp-wasm is a good example, but shows we need to use something other than tokio.
after that we would encounter threads, and the route filesystem stuff through workspace.fs.

I believe workspace.fs is probably vscode-specific, so we'd need to keep around the existing direct-to-filesystem code
and either make the web-extension a feature or entire branch at first...

I think it is worth pursuing, perhaps after the diagnostics are a bit more friendly

Edit:
Also need to look at vscode-wasm which if I understand, could eventually allow us to replace the entirety of the javascript with rust compiled to wasm, this seems like it should be possible as we aren't spawning any processes doing things not supported by wasi itself other than filesystem stuff discussed above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant