-
-
Notifications
You must be signed in to change notification settings - Fork 126
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
Enable your extension to run on VS Code on the web #1554
Comments
Thank you for asking about this. I would like to get it working. I'm going to need to find some funding for these changes. |
@Jason3S glad to hear you would like to get it working! Especially since some members of our team use your extension actively and we would like to continue using it in the web 😊 I know @aeschli took a look at your extension and he came to the same conclusion that it might be substantial amount of work to get it working. |
@Jason3S I'd also be interested in this feature because I believe this is required for Spell Checker to work with live share as well. I see you've started work on this. Do you have any estimates for when this will be ready? |
The Spell Checker v4 will have support for virtual workspaces and remote development. You can try an alpha version from Releases · streetsidesoftware/vscode-spell-checker. Manual Installation
|
Related to (#1554 Live Share Comment)[#1554 (comment)]
👋 I'm Isidor, a PM from the VS Code team, and we recently announced VS Code for the Web at https://vscode.dev/, which provides a free, zero-install Microsoft Visual Studio Code experience running entirely in your browser. You can learn more here.
We'd like to ensure Spell Checker can run in the web, and we have a guide for enabling extensions for the web here. As a couple of highlights:
browser
propertyvscode.workspace.fs
Looking at your extension the effort to transition to web will not be straight forward, however I wanted to create this issue so we start a discussion. Let us know if we can help.
fyi @aeschli since I know you also planned to look into this extension
Thank you!
The text was updated successfully, but these errors were encountered: